feat: add automated release workflow (tag-triggered)#943
Open
cloud-game-development-toolkit-bot wants to merge 1 commit into
Open
feat: add automated release workflow (tag-triggered)#943cloud-game-development-toolkit-bot wants to merge 1 commit into
cloud-game-development-toolkit-bot wants to merge 1 commit into
Conversation
cloud-game-development-toolkit-bot
requested a review
from a team
as a code owner
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
Adds a release workflow triggered by pushing a semver tag (v*). This replaces the manual multi-step release process with a single git tag push. Guard rails for public repo safety: - Validates the tag points to a commit on main - Requires an existing release-drafter draft (ensures PRs were merged) - Tag protection rules (configured in repo settings) restrict who can push tags Workflow steps: 1. Validates tag is on main branch 2. Verifies a draft release exists 3. Generates changelog via git-chglog and commits to main 4. Force-moves version and latest tags to include changelog commit 5. Publishes the draft release with the version tag Docs deployment triggers automatically via docs-deploy-version.yml on release publish. Closes #942
cloud-game-development-toolkit-bot
force-pushed
the
feat/automated-release-workflow
branch
from
0895e19 to
99f4669
Compare
cloud-game-development-toolkit-bot
changed the title
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
2 participants
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.
Summary
Adds a release workflow triggered by pushing a semver tag. A maintainer releases by running:
The workflow handles everything else: changelog generation, tag management, and publishing the GitHub release. Docs deployment fires automatically via the existing
docs-deploy-version.yml.Guard rails
v*tagsWorkflow steps
push: tags: ["v[0-9]+.[0-9]+.[0-9]+*"]maingit-chglog, commits to mainlatestto include changelog commitSLSA compliance
No
workflow_dispatchinputs — the version is derived from the tag ref (github.ref_name), which SLSA considers the build entry point, not a user parameter. Passes CKV_GHA_7.What this replaces
git tag && git pushlatesttagCloses #942