feat: release bump path after renovate-only merges#106
Merged
Conversation
Co-authored-by: swibrow <15628653+swibrow@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Bump release version after merging Renovate PRs
feat: document Mar 20, 2026
feat: release bump path after Renovate-only merges
swibrow
changed the title
feat: release bump path after Renovate-only merges
github-actions
Bot
added
the
documentation
tamedia-fission Bot
pushed a commit
that referenced
this pull request
Mar 20, 2026
## [3.21.0](v3.20.0...v3.21.0) (2026-03-20) ### ✨ Features * release bump path after renovate-only merges ([#106](#106)) ([4e68e55](4e68e55))
|
🎉 This PR is included in version 3.21.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
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.
Description
Renovate PRs were merged without producing a new release; this PR adds explicit guidance for forcing the next minor release.
It updates release docs so maintainers can intentionally trigger semantic-release with a
feat:commit when changes are maintenance-only.README.mdunder Releases to document the bump path for Renovate-only merge sequences.feat:=> minor version bump.Motivation and Context
Recent dependency-update merges did not produce a version bump, creating release drift.
This change makes the release-trigger mechanism explicit to avoid repeating that gap.
Breaking Changes
No.
How Has This Been Tested?
.github/workflows/_test-*.yamlto demonstrate and validate my change(s)pre-commit run -aon my pull requestmake gen_docs_runon my pull requestGithub Conventional Commit Release
https://dnd-it.github.io/github-workflows/workflows/gh-release/
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.