From ae994ba47ba3d2115510dbd3f08e931e18cb0232 Mon Sep 17 00:00:00 2001 From: Todd Anderson Date: Wed, 28 Oct 2026 14:44:49 -0400 Subject: [PATCH] chore: bump minor rather than major for pre-1.0 breaking changes MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Matches the sibling provider repos' release-please configuration. Without this flag, release-please's default versioning escalates any breaking change to a major bump even below 1.0.0 — the fix! in #64 retitled the open release PR (#72) to 1.0.0 instead of 0.9.0. The 1.0 milestone should be a deliberate decision, not a side effect of a config gap. --- release-please-config.json | 1 + 1 file changed, 1 insertion(+) diff --git a/release-please-config.json b/release-please-config.json index 5e913a7..900d74d 100644 --- a/release-please-config.json +++ b/release-please-config.json @@ -3,6 +3,7 @@ ".": { "release-type": "python", "versioning": "default", + "bump-minor-pre-major": true, "include-v-in-tag": false, "extra-files": ["docs/conf.py", "ld_openfeature/version.py"], "include-component-in-tag": false