Skip to content

chore(release): set the release baseline to the rewritten 0.1.0 commit #13

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kvlonge merged 1 commit into from
Oct 31, 2026
Merged

chore(release): set the release baseline to the rewritten 0.1.0 commit #13

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .github/RELEASING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
1 change: 1 addition & 0 deletions release-please-config.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,5 @@
{
"last-release-sha": "5bbc73b00eb362e633a88cf8f7de82747941f1f7",
"packages": {
".": {
"release-type": "python",
Expand Down
Loading