ci(release): embed semantic-release version in Docker build#128
Merged
Conversation
…tagging The sidebar shows "v0.1.0" because the Docker build checks out the git tag, but @semantic-release/npm updates package.json without committing it. Adding @semantic-release/git commits the updated package.json and package-lock.json before the tag is created, so the Docker image gets the correct version. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Contributor
|
🎉 This PR is included in version 1.8.0-beta.23 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Contributor
|
🎉 This PR is included in version 1.8.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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
@semantic-release/git(v10.0.1) to the semantic-release plugin chainpackage.jsonandpackage-lock.jsonbefore the git tag is created, so the Docker build picks up the correct version instead of the static0.1.0placeholdernpm(updates version) →git(commits files with[skip ci]) →github(creates release)Problem
The sidebar shows
Cornerstone v0.1.0because:@semantic-release/npmupdatespackage.jsonin the working directory@semantic-release/git, nothing commits that change0.1.0Test plan
beta, confirm the release workflow produces achore(release): X.Y.Z-beta.N [skip ci]commit🤖 Generated with Claude Code