fix(components): preserve stack version on update when no version flag given#427
Merged
fix(components): preserve stack version on update when no version flag given#427
Conversation
added 3 commits
April 21, 2026 10:21
…g given cy component update without --stack-branch/--stack-tag/--stack-commit-hash was silently switching the component to the catalog default branch instead of keeping the current version. Fix: resolve the current component's ServiceCatalog.Version against the stack version list and pass it through; fall back to catalog default only if the version can no longer be found. Add e2e regression test TestUpdatePreservesStackVersionWhenNotSpecified.
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
1 participant
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.
fix(components): preserve stack version on update when no version flag given
cy component update without --stack-branch/--stack-tag/--stack-commit-hash
was silently switching the component to the catalog default branch instead
of keeping the current version.
Fix: resolve the current component's ServiceCatalog.Version against the
stack version list and pass it through; fall back to catalog default only
if the version can no longer be found.
Add e2e regression test TestUpdatePreservesStackVersionWhenNotSpecified.