chore(release): pin release-please baseline to the v0.29.2 commit

[sunib]

Problem

release-please PR #196 proposes a bogus 0.30.0 that re-lists 168 already-shipped commits and re-declares breaking changes that released back in v0.28.0. It is fresh (created right after 0.29.2, Release Please job succeeded), so this is live misbehaviour, not a stale PR.

Root cause: the failed 0.29.1 release was manually deleted. Its GitHub release is gone (tag still present, no release), which broke release-please's last-release tracking — it walked back to ~v0.27.1 as its baseline.

Meanwhile main sits exactly on the v0.29.2 tag with 0 commits after it, and v0.29.2 itself is a fully-signed, verified release (image + chart signatures, SLSA provenance, SPDX SBOM all check out). So there is genuinely nothing to release right now.

Fix

Pin last-release-sha to the v0.29.2 release commit (7a53779c6a8da0dbff72940011c34396a85530cc) so release-please only considers commits after 0.29.2.

• On the next release-please run (this PR merging to main), it will find no releasable commits and close/empty chore(main): release gitops-reverser 0.30.0 #196.
• Future releases bump correctly from 0.29.2 (feat → 0.30.0, fix/perf → 0.29.3) with only real new commits in the changelog.
• Typed chore(release): — non-bumping, so it does not itself trigger a release.
• Reversible: the pin can be removed after the next clean release once the tag chain is trusted again.

Do not merge #196

Merging it would tag 0.30.0 on a commit identical to 0.29.2 and re-announce already-shipped breaking changes. Merge this PR instead, confirm #196 auto-closes.

Follow-up (separate, destructive — not in this PR)

The failed 0.29.1 also left orphans to clean up: the stray gitops-reverser-v0.29.1 git tag, and unsigned partial :0.29.1 artifacts in GHCR (image + chart).

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Updated release tracking metadata to point to the latest commit anchor for future release generation.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 22e464ae-2177-4080-aaf2-9d2e4d79a7e2

📥 Commits

Reviewing files that changed from the base of the PR and between 7a53779 and 996efe4.

📒 Files selected for processing (1)

• release-please-config.json

---

📝 Walkthrough

Walkthrough

The last-release-sha field in release-please-config.json was updated to a new commit SHA, changing the reference point used by Release Please for release history tracking.

Changes

Release Config Update

Layer / File(s)	Summary
Update last-release-sha release-please-config.json	The root package configuration's last-release-sha value was changed to a new commit SHA.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is detailed, but it does not follow the required template sections like Type of Change, Testing, Checklist, and Related Issues.	Rewrite the PR description using the repository template and add the missing sections, including type of change, testing, checklist, and related issues.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the main change: pinning release-please's baseline to the v0.29.2 commit.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/release-please-baseline

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!