chore: update version to 1.22.5-beta-1 in package.json and package-lock.json; add CommonContextDataType to types.ts#1005
Merged
Conversation
…ck.json; add CommonContextDataType to types.ts
There was a problem hiding this comment.
Pull request overview
This pull request bumps the package version to 1.22.5-beta-1 and introduces a new shared type definition CommonContextDataType to standardize context data structures with optional uiMarkup support for AI agent contexts.
Changes:
- Updated package version from 1.22.5-beta-0 to 1.22.5-beta-1 in package.json and package-lock.json
- Added
CommonContextDataTypetype definition to encapsulate shared context properties with optionaluiMarkupfield - Applied
CommonContextDataTypetoRESOURCE_BROWSER_CLUSTERandexternalFluxAppcontext types
Reviewed changes
Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| package.json | Version bump to 1.22.5-beta-1 |
| package-lock.json | Version bump to 1.22.5-beta-1 |
| src/Shared/Providers/MainContextProvider/types.ts | Added CommonContextDataType and applied it to two AI agent context source types |
Comments suppressed due to low confidence (1)
src/Shared/Providers/MainContextProvider/types.ts:99
- The
CommonContextDataTypeis only applied toexternalFluxApp(line 104) but not to the other app types (devtronApp,devtronHelmChart,externalHelmChart,externalArgoApp). This creates inconsistency where some app types supportuiMarkupand other dynamic properties while others don't. Consider applyingCommonContextDataTypeto all app types within theAPP_DETAILSsource for consistency, or document why onlyexternalFluxApprequires this additional data structure.
| AIAgentAppDataType<
'devtronApp' | 'devtronHelmChart',
'appId' | 'appName' | 'envId' | 'envName' | 'clusterId'
>
| AIAgentAppDataType<'externalHelmChart', 'appId' | 'appName' | 'clusterId' | 'namespace'>
| AIAgentAppDataType<'externalArgoApp', 'appName' | 'clusterId' | 'namespace'>
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
vivek-devtron
approved these changes
Jan 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This pull request introduces a minor version bump and refactors the context type definitions to improve consistency and maintainability. The main focus is on standardizing shared context data structures for AI agent contexts.
Version update:
package.jsonfrom1.22.5-beta-0to1.22.5-beta-1.Type definition improvements:
CommonContextDataTypetype intypes.tsto encapsulate shared context properties, including an optionaluiMarkupfield.AIAgentContextTypetype intypes.tsto useCommonContextDataTypefor bothAPP_DETAILSandRESOURCE_BROWSER_CLUSTERsources, replacing the previous use ofRecord<string, unknown>.Type of change
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist