Skip to content

feat!: before 1.0.0, a feat title gives a patch release - #3

Merged
michal-giergielewicz merged 1 commit into
mainfrom
feat/pre-major-feat-is-patch
Nov 15, 2026
Merged

michal-giergielewicz merged 1 commit into
mainfrom
feat/pre-major-feat-is-patch

Conversation

@michal-giergielewicz

Copy link
Copy Markdown
Contributor

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). A feat: title also gave a minor release, so fix:, perf: and revert: 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.

PR title Change from 1.0.0 Change before 1.0.0
feat!: …, or BREAKING CHANGE: in the PR body major minor
feat: … minor patch (was minor)
fix: …, perf: …, revert: … patch patch
docs:, test:, ci:, build:, refactor:, chore:, style: none none
  • New function effective_level(version, level); bump() uses it.
  • The plan (the version job table) reports the level that applies to the current version.
  • The step down applies to min_bump too: "min_bump": "minor" on a 0.x package gives a patch.

Effect on the repos of the organization

  • A repo gets the new rule only when it moves its pinned SHA of freyr/.github/actions/* to this release.
  • Each 0.x package changes: a feat: title gives a patch release, and a minor release needs ! or BREAKING CHANGE:. This includes the 0.x plugins of freyr-claude-plugin and message-broker.
  • A package at 1.0.0 or above does not change.

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 to feat: if a 1.1.0 release is preferred.

Checks

  • Unit tests: 20 pass (2 new tests, 1 changed expectation).
  • ruff check and ruff format --check: clean.

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.
@michal-giergielewicz
michal-giergielewicz merged commit b0c5431 into main Nov 15, 2026
6 checks passed
@michal-giergielewicz
michal-giergielewicz deleted the feat/pre-major-feat-is-patch branch November 15, 2026 17:25
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant