From 996efe4792c2d9e14e7289617bd397e5678926ca Mon Sep 17 00:00:00 2001 From: Simon Koudijs Date: Mon, 6 Jul 2026 05:27:02 +0000 Subject: [PATCH] chore(release): pin release-please baseline to the v0.29.2 commit release-please lost its last-release baseline after the failed 0.29.1 release was manually deleted: with the 0.29.1 GitHub release gone (its tag still present, but no release), release-please walked back to ~v0.27.1 and opened a release PR (#196) proposing 0.30.0 that re-lists 168 already-shipped commits and re-declares breaking changes released back in v0.28.0. Pin last-release-sha to the v0.29.2 release commit (7a53779c6a8da0dbff72940011c34396a85530cc) so release-please only considers commits after 0.29.2. main is currently exactly at that commit (0 commits after), so on the next run release-please will find nothing to release and close/empty #196. Future releases then bump correctly from 0.29.2. Non-bumping (chore) so this change does not itself trigger a release. The pin can be removed after the next clean release once the tag chain is trusted again. Co-Authored-By: Claude Opus 4.8 (1M context) --- release-please-config.json | 1 + 1 file changed, 1 insertion(+) diff --git a/release-please-config.json b/release-please-config.json index a3043bf4..697182f7 100644 --- a/release-please-config.json +++ b/release-please-config.json @@ -3,6 +3,7 @@ ".": { "release-type": "simple", "package-name": "gitops-reverser", + "last-release-sha": "7a53779c6a8da0dbff72940011c34396a85530cc", "bump-minor-pre-major": true, "draft": true, "changelog-sections": [