ci: create GitHub releases for release candidate branches #7862
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.
Problem
The AWS Toolkit VSCode project lacked a streamlined release candidate workflow. Creating release candidates would require manual branch creation and version management.
Solution
Added automated release candidate support:
Created
.github/workflows/setup-release-candidate.yml- Workflow to create RC branches with automatic version bumpingSupports
Major/Minor/Patch/Customversion incrementsReads and increments both
toolkitandamazonqpackage versions independentlyCreates date-based RC branches (
rc-YYYYMMDD)Commits version changes and pushes the RC branch
Updated
.github/workflows/release.yml- Added support forrelease/*branchesAutomatically creates
rc-*prefixed releases for release candidate branchesProper release naming for RC artifacts
This enables a clean RC workflow: trigger the setup workflow with a commit ID and version increment type, then the release pipeline automatically handles the rest.
feature/xbranches will not be squash-merged at release time.