From 57c63d59cf8d162ef23604ad3d1f27d9d8e9dfad Mon Sep 17 00:00:00 2001
From: Kevin Longe <273747162+kvlonge@users.noreply.github.com>
Date: Sat, 31 Oct 2026 08:36:26 +0000
Subject: [PATCH] chore(release): set the release baseline to the rewritten
 0.1.0 commit

main was rewritten to drop tool attribution trailers, so the v0.1.0 tag
is no longer an ancestor of main. last-release-sha points Release Please
at the rewritten 0.1.0 release commit.
---
 .github/RELEASING.md       | 5 +++++
 release-please-config.json | 1 +
 2 files changed, 6 insertions(+)

diff --git a/.github/RELEASING.md b/.github/RELEASING.md
index ca0d8c6..015ccd9 100644
--- a/.github/RELEASING.md
+++ b/.github/RELEASING.md
@@ -34,6 +34,11 @@ run that leaves the release pull request unchanged does not repair it. To recove
 release pull request, then merge the next up-to-date pull request; Release Please opens a fresh
 release pull request from the verified tree.
 
+`main` was rewritten after 0.1.0 to drop tool attribution trailers, with every tree unchanged, so
+the `v0.1.0` tag points at the pre-rewrite commit and is not an ancestor of `main`.
+`last-release-sha` in `release-please-config.json` names the rewritten 0.1.0 release commit, so
+Release Please collects only the commits after it.
+
 ## One-time setup
 
 A repository administrator does these once, in a browser:
diff --git a/release-please-config.json b/release-please-config.json
index e6eeb12..ef4b0cc 100644
--- a/release-please-config.json
+++ b/release-please-config.json
@@ -1,4 +1,5 @@
 {
+  "last-release-sha": "5bbc73b00eb362e633a88cf8f7de82747941f1f7",
   "packages": {
     ".": {
       "release-type": "python",