chore: fix 2025-1-RC5 publish commit history - #272
Merged
Conversation
This reverts commit 28911db.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
anilturkmayali
approved these changes
Aug 31, 2026
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
2 participants
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.
What this PR changes/adds
Corrects the merge of #270. That PR was squash-merged, which collapsed its
two intentional commits — one setting
specStatus: "base"for the releasesnapshot, one reverting it — into a single final-state commit. This dropped
the
"base"-status commit entirely, so there is nothing onmainthat2025-1-RC5can correctly be tagged against.This PR:
28911db("chore: publish 2025-1-RC5 (chore: publish 2025-1-RC5 #270)")Net file content is unchanged — verified identical to current
mainviagit diff origin/main HEAD. Only the commit history is restored.This PR must be merged with "Rebase and merge." Not squash — that's
exactly what caused this. Click the dropdown arrow next to the merge button
and select "Rebase and merge" explicitly.
Linked Issue(s)
Relates to #269