From 6b092c16e5d232de4802b24dc92400832030d0b6 Mon Sep 17 00:00:00 2001 From: Venkat Date: Sun, 30 Aug 2026 16:01:18 +0000 Subject: [PATCH] fix: set initial-version so the first release is v0.0.1, not v1.0.0 release-please proposed 1.0.0 for the first release. The bump flags do not apply to it: bump-patch-for-minor-pre-major is documented as "feature changes only bump semver patch if version < 1.0.0", so it governs bumping *from* an existing version - and there is no existing version yet. A 0.0.0 manifest entry is not treated as a released version either, so release-please fell back to its default first release of 1.0.0. initial-version is the option that covers this case: "releases the initial library with a specified version". The bump flags stay - they are still what keeps subsequent feature releases on 0.0.x rather than jumping to 0.1.0. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_01NiwgsqcQ4JikhFYj4NHEjM --- release-please-config.json | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/release-please-config.json b/release-please-config.json index e386a06..09a340d 100644 --- a/release-please-config.json +++ b/release-please-config.json @@ -20,7 +20,8 @@ "packages": { ".": { "release-type": "simple", - "package-name": "toolbox" + "package-name": "toolbox", + "initial-version": "0.0.1" } } }