ci(gha): automate semantic release flow for Docker app#206
Merged
Conversation
louib
previously approved these changes
May 22, 2026
Previously, releases required a manual package.json version bump commit to trigger the workflow. This was error-prone and relied on a fragile diff-detection heuristic. Going forward, releases are triggered manually via workflow_dispatch in GitHub Actions. When run, semantic-release reads all commits since the last tag, determines the next version (feat: → minor, fix: → patch, feat!: → major), creates a git tag and GitHub Release with generated notes, then runs a Trivy security scan and pushes the Docker image to GHCR. chore:/test:/ci: commits never trigger a release. PRs can merge to master freely without cutting a release. Changes: - package.json version set to "0.0.0-semantically-released" placeholder; git tags are now the authoritative version source - .releaserc.json: add @semantic-release/github plugin to create git tags and GitHub Releases natively - release-to-ghcr.yaml: replace get-context + create-release jobs with a single semantic-release step; trigger changed to workflow_dispatch; add concurrency group to prevent overlapping releases Note: v3.0.0 tag already exists on master and will serve as the baseline for semantic-release on first run. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
pranishnepal
commented
May 22, 2026
| push: | ||
| branches: | ||
| - master | ||
| workflow_dispatch: |
Contributor
Author
There was a problem hiding this comment.
changed so that the new version is released on workflow start, as opposed to master merge
louib
approved these changes
May 22, 2026
Contributor
pranavjain97
left a comment
pranavjain97
left a comment
There was a problem hiding this comment.
overall lgtm, just a bit concerned about confusing clients on the image release versioning with this change so it should be clarified somewhere in the changelogs / dev-docs
| { | ||
| "name": "@bitgo/advanced-wallets", | ||
| "version": "3.0.0", | ||
| "version": "0.0.0-semantically-released", |
Contributor
There was a problem hiding this comment.
once we do a new release via GH, what will the release tag and image numbering look like? It could be a bit confusing since the last image release was 3.0.0
Contributor
Author
There was a problem hiding this comment.
it should be 3.0.1 (if it's a feat), tag 3.0.0 already exists. This version here will stay constant
pranavjain97
approved these changes
May 22, 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
3 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.
Problem
Currently, releases required a manual package.json version bump commit to trigger the workflow. This was error-prone and relied on a fragile diff-detection heuristic.
What
Going forward, merging a
feat:orfix:commit to master automatically triggers semantic-release, which determines the next version from commit history, creates a git tag (e.g. v3.1.0) and GitHub Release, then gates the Trivy scan and Docker build on the release output.chore, test, cicommits produce no release.The versioning in
package.jsonsays static. We do something similar inapi-ts.Notes
release-to-ghcr.yaml: replacedget-context+create-releasejobs with a singlesemantic-releasestep; addedconcurrency groupto prevent overlapping releases.