From d1534f1d95e2ef23e8be67bce9a621b594118db5 Mon Sep 17 00:00:00 2001 From: ShocOne <62835948+ShocOne@users.noreply.github.com> Date: Thu, 30 Jul 2026 15:20:37 +0100 Subject: [PATCH] fix: release the toolkit as 0.1.0 rather than 1.0.0 release-please succeeded for the first time and opened a release PR for 1.0.0. That is not a breaking change being detected -- the history rewrite removed the only feat!: and BREAKING CHANGE: markers, and main now carries neither. It is the initial-release default. strategies/base.js returns Version.parse('1.0.0') unless initial-version is configured, and since no tag exists release-please took that path rather than bumping the manifest's 0.0.0. The bump rule itself would have given 0.1.0: features with no breaking change is a MinorVersionUpdate, and pre-major only diverts to a patch when bump-patch-for-minor-pre-major is set. So initial-version is now 0.1.0, which is also the honest number. 1.0.0 claims an API somebody can depend on, and the blueprint format is at version 3 having moved three times in this phase alone, with two roadmap phases still outstanding. Co-Authored-By: Claude Opus 5 (1M context) --- release-please-config.json | 17 ++++++++++++++--- 1 file changed, 14 insertions(+), 3 deletions(-) diff --git a/release-please-config.json b/release-please-config.json index 89c6ddcc..a0c625b7 100644 --- a/release-please-config.json +++ b/release-please-config.json @@ -1,6 +1,7 @@ { "$schema": "https://raw.githubusercontent.com/googleapis/release-please/main/schemas/config.json", "release-type": "go", + "initial-version": "0.1.0", "include-component-in-tag": false, "packages": { ".": { @@ -9,8 +10,18 @@ } }, "changelog-sections": [ - { "type": "feat", "section": "Features" }, - { "type": "fix", "section": "Bug Fixes" }, - { "type": "chore", "section": "Chores", "hidden": true } + { + "type": "feat", + "section": "Features" + }, + { + "type": "fix", + "section": "Bug Fixes" + }, + { + "type": "chore", + "section": "Chores", + "hidden": true + } ] }