From 539c536dea051a6ff58597e287e7a3d552a445fd Mon Sep 17 00:00:00 2001 From: David Cozens Date: Wed, 22 Apr 2026 20:21:46 +0100 Subject: [PATCH] chore: configure release-please to stay on 0.x until 1.0 is explicitly cut MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Add bump-minor-pre-major: true so any Conventional-Commits-breaking change (feat!: or BREAKING CHANGE footer) during the 0.x series maps to a 0.x → 0.(x+1) minor bump rather than the default jump to 1.0.0. Matches the release policy: 0.x is the beta series where breaking changes are expected; 1.0.0 signals API stability and is cut deliberately. The standing release-please PR (#101) will re-render to propose 0.1.0 rather than 1.0.0 on the next push to main. --- release-please-config.json | 1 + 1 file changed, 1 insertion(+) diff --git a/release-please-config.json b/release-please-config.json index 20e6e2e0..d86e1010 100644 --- a/release-please-config.json +++ b/release-please-config.json @@ -2,6 +2,7 @@ "packages": { ".": { "release-type": "simple", + "bump-minor-pre-major": true, "changelog-sections": [ { "type": "feat", "section": "Features" }, { "type": "fix", "section": "Bug Fixes" },