Repository navigation
feat!: before 1.0.0, a feat title gives a patch release - #3
Merged
Merged
Conversation
Before 1.0.0 each version level now moves one step down: a breaking change (! or BREAKING CHANGE) is a minor release, and a feat title is a patch release. Until now only the breaking change moved down, so a feat title gave a minor release and fix, perf and revert were the only titles for a patch release. From 1.0.0 the rule does not change. The plan reports the level that applies to the current version.
20 of 86 tasks
michal-giergielewicz
added a commit
to freyr/message-broker
that referenced
this pull request
Nov 15, 2026
Phase 0 of #20: move the pinned `freyr/.github` actions from v1.0.1 to v2.0.0 (`b0c5431`). v2.0.0 changes the version rule before 1.0.0 (freyr/.github#3): | PR title | Release of this repo | |---|---| | `feat!: …`, or `BREAKING CHANGE:` in the PR body | minor | | `feat: …` | patch (was minor) | | `fix: …`, `perf: …`, `revert: …` | patch | ## Changes - `pr.yml`, `release.yml`, `tests.yml`: four pins to v2.0.0. - `README.md`: the status note states the version policy of the 0.x line. The `pr-title`, `version` and `ci-gate` checks of this pull request already run with the v2.0.0 actions.
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.
Problem
A package that stays on 0.x has this version policy: a major change is a minor release, and a smaller improvement is a patch release.
The release rule did not permit that. Before 1.0.0 only the breaking change moved one step down (
feat!→ minor). Afeat:title also gave a minor release, sofix:,perf:andrevert:were the only titles for a patch release. A small improvement then needed a wrong title.Change
Before 1.0.0 each level moves one step down. From 1.0.0 the rule does not change.
feat!: …, orBREAKING CHANGE:in the PR bodyfeat: …fix: …,perf: …,revert: …docs:,test:,ci:,build:,refactor:,chore:,style:effective_level(version, level);bump()uses it.versionjob table) reports the level that applies to the current version.min_bumptoo:"min_bump": "minor"on a 0.x package gives a patch.Effect on the repos of the organization
freyr/.github/actions/*to this release.feat:title gives a patch release, and a minor release needs!orBREAKING CHANGE:. This includes the 0.x plugins offreyr-claude-pluginandmessage-broker.Version of this repo
The title has
!because the same PR title now gives a different version in a consumer repo. This repo is at 1.x, so the release is 2.0.0. Change the title tofeat:if a 1.1.0 release is preferred.Checks
ruff checkandruff format --check: clean.