Repository navigation
chore(release): set the release baseline to the rewritten 0.1.0 commit - #13
Merged
Merged
Conversation
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.
Deploying sqlclean with
|
| Latest commit: |
57c63d5
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://8a455912.sqlclean.pages.dev |
| Branch Preview URL: | https://chore-release-baseline.sqlclean.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
mainwas rewritten to drop tool attribution trailers, with every tree unchanged. Thev0.1.0tag and release keep pointing at the pre-rewrite commita128aec, which is no longer an ancestor ofmain, so Release Please can no longer find the last release on the branch and would propose a release built from every commit since the start.Changes
release-please-config.json:last-release-shais5bbc73b, the rewrittenchore(main): release 0.1.0 (#6)commit, whose tree is identical toa128aec..github/RELEASING.md: one paragraph explaining why the setting exists.Verification
5bbc73bis an ancestor ofmainand has the same tree as the taggeda128aec.