Repository navigation
fix: unify semantic-release policy and dynamic sign-off - #93
Merged
Merged
Conversation
Signed-off-by: Dmitrii Safronov <zimniy@cyberbrain.cc>
Owner
Author
|
🎉 This PR is included in version 1.0.4-rc.2 🎉 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
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.
Keep the existing
releasestable /mainRC model, align common release-rule ordering with the bundled config, and deriveSigned-off-byfromgit var GIT_COMMITTER_IDENTinstead of a hardcoded identity.Preserve
@semantic-release/exec, its TOML preparation, and Git assets for CHANGELOG.md, pyproject.toml, and uv.lock. Actual prepare tests verify1.2.0-rc.1→1.2.0rc1and1.2.0-rc.12→1.2.0rc12, updating the own-package lock record while preserving all other parsed project/lock data. The existing RC conversion was executed successfully before editing and is unchanged.Rollout: this PR targets main. The release branch retains its old config until the normal reviewed main → release promotion; this PR does not directly edit release or trigger that promotion.
Validation used semantic-release 25.0.2 from the published Docker image pinned at
ghcr.io/disafronov/semantic-release@sha256:1d3bf05412d10cef19d69a90107127a5f2c05b51f6f7e068335389bf419b0b24(network disabled). The 81-test cross-repository harness passed. For this configuration it checks real plugin loading/order, all common release rules including breaking changes, two different Git committer identities, and the actualpreparepipeline for stable, RC.1, and RC.12. Prepare runs against temporary local Git remotes, including the generated commit and assets, without creating real tags or publishing packages. Branch expansion and version progression were rehearsed with this repository's actual tags and semantic-release Git notes; the candidate patch versions do not collide with existing tags.git diff --checkpasses.The shared
semantic.ymlis identical to all three current source templates and is unchanged. No/optextends or other image-internal configuration dependency is introduced. No release, real release branch, tag, package publication, or PR merge is performed by this change.