From 0ff631aa76db27f638d706fd6142dea8f2226613 Mon Sep 17 00:00:00 2001 From: "Tj (bougyman) Vanderpoel" Date: Tue, 11 Aug 2026 16:30:33 -0400 Subject: [PATCH] chore: pin the next release to 1.0.0 via release-as The graduation commit (#70) manually set the manifest to 1.0.0 in the same commit that also carried a `!` breaking marker - release-please treated that marker as new unreleased work on top of the manifest we'd already bumped, computing 1.0.0 + major = 2.0.0 (PR #71, closed unmerged, never tagged/released). Pinning release-as: 1.0.0 tells release-please to target exactly 1.0.0 for its next PR instead of computing a bump on top of the current manifest value. Per release-please's own docs, this should be removed (or bumped) once that 1.0.0 release PR merges, or later runs will keep reusing it. --- .release-please-config.json | 1 + 1 file changed, 1 insertion(+) diff --git a/.release-please-config.json b/.release-please-config.json index 7d924c8..5e214ed 100644 --- a/.release-please-config.json +++ b/.release-please-config.json @@ -3,6 +3,7 @@ ".": { "changelog-path": "CHANGELOG.md", "release-type": "simple", + "release-as": "1.0.0", "bump-minor-pre-major": false, "bump-patch-for-minor-pre-major": false, "draft": false,