docs(release): backfill v1.2.0 notes#6
Merged
Conversation
Stage uv.lock after the release build so semantic-release includes it in the version commit without uploading it as a GitHub Release asset.
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
1 participant
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
uv.lockexplicitly for future semantic-release version commitsuv.lockas a GitHub Release assetRoot cause
The stacked v1.2 branch was created before v1.1 was released, then merged with v1.1 in its ancestry. Python Semantic Release found the feature commit for version calculation but assigned it to the earlier tagged release while traversing the graph for changelog generation.
Validation
tox run -e lint,test(49 tests passed)uv lock --check --no-configdocsandchorecommits do not produce a new release