From ceb526d02bb29a6d6a002590ad36e8de7f580b83 Mon Sep 17 00:00:00 2001 From: Simon Schrottner Date: Wed, 14 Oct 2026 16:26:03 +0200 Subject: [PATCH] chore: release the conformance assets as 0.1.0, not 1.0.0 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit release-please opened #447 proposing 1.0.0. The manifest entry is "0.0.0", which it reads as "no release yet", and it then falls back to its default initial version of 1.0.0 — bump-minor-pre-major never gets a chance to apply, because there is no prior version to bump. 1.0.0 would be a claim this does not mean. Appendix F describes these assets as experimental and is not merged yet; the capability vocabulary, the control-API surface and the report schema are all still under review, and a 1.0.0 Go module says the opposite to anyone running `go get`. initial-version pins the first release to 0.1.0, leaving the patch digit for fixture corrections and the minor for new scenarios, both of which are expected. Once this merges release-please will re-propose #447 at 0.1.0. Signed-off-by: Simon Schrottner --- release-please-config.json | 1 + 1 file changed, 1 insertion(+) diff --git a/release-please-config.json b/release-please-config.json index b346fefd..4a3aa49a 100644 --- a/release-please-config.json +++ b/release-please-config.json @@ -21,6 +21,7 @@ "include-component-in-tag": true, "changelog-path": "CHANGELOG.md", "bump-minor-pre-major": true, + "initial-version": "0.1.0", "versioning": "default", "extra-files": [] }