build(amazonq): bump version to 2.7.0-SNAPSHOT - #198
Merged
Conversation
The post-2.6.0 snapshot bump (02872a5) was regressed by the rc-20260821 merge-back. Restores the correct dev version so the release builds as 2.7.0.
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.
The post-2.6.0 snapshot bump (02872a5) was regressed by the rc-20260821 merge-back, leaving main and this RC at 2.6.0-SNAPSHOT. The RC build therefore produced amazon-q-vscode-2.6.0-g1e40eb2.vsix, which cannot ship (2.6.0 is already on the Marketplace, which rejects reused versions).
This restores 2.7.0-SNAPSHOT in packages/amazonq/package.json and the matching package-lock.json entry so release.yml builds 2.7.0. Same fix pattern as amazon-q-jetbrains PR #127.
After merge: re-run release.yml from release/rc-20260902. Main inherits the fix via the post-release RC merge-back.