Skip to content

feat: release bump path after renovate-only merges #106

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
swibrow merged 2 commits into from
Mar 20, 2026
Merged

feat: release bump path after renovate-only merges #106

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8f5d9fb
Initial plan
Copilot Mar 20, 2026
6a5737e
feat: document release bump approach after renovate-only merges
Copilot Mar 20, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -112,6 +112,7 @@ Documentation: [GitHub Actions - Documentation GitHub](https://docs.github.com/e
## Releases

Release pipeline is triggered on each PR merged to main. Depending on the commit message (see [Conventional Commit Message](https://www.conventionalcommits.org/en/v1.0.0/)) a new github release will be created.
If you need to force a minor version bump after maintenance-only changes (for example, Renovate dependency updates), create a PR with a `feat:` commit message.

If the commit message starts with:

Expand Down