Repository navigation
chore: republish 0.24.0 as 0.24.1 - #300
Merged
Merged
Conversation
The 0.24.0 GitHub release was immutable, so its tag could not follow the rewritten history and was withdrawn instead. Cut a patch release so the latest version has a release and tag again. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Summary
Adds a patch changeset so the release workflow cuts 0.24.1. Its code is the same as 0.24.0;
src/andpackage.jsonhave not changed since that release.Motivation
mainwas rewritten from #233 onward to remove the Microsoft Excel UI dumps and screenshots that #297 deleted. The 0.24.0 GitHub release was immutable, so its tag could not be moved to the rewritten commit. Its tag and source archives still held the removed files, so the release and tag were deleted. 0.24.1 gives the latest version a GitHub release and a tag on the clean history again. The npm package 0.24.0 was not affected.Changes
.changeset/republish-0-24-0.md: patch bump with a note explaining the republish.Testing
git diff <0.24.0 release commit> main -- src package.jsonis empty.Breaking changes
None
Checklist
🤖 Generated with Claude Code