Repository navigation
chore: release 0.24.0 - #57
Merged
Merged
Conversation
Co-Authored-By: Claude Sonnet 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
Release 0.24.0 of
@behindthemusictree/ui. The only change sincev0.23.0isFloatingToggle(#56), a single-cell floatingaria-pressedtoggle for placing besideZoomControls.Changes
packages/ui/package.json: 0.23.0 → 0.24.0 (minor: new export, no breaking change).CHANGELOG.md:[Unreleased]moved to[0.24.0] - 2026-11-12.Test plan
pnpm release -- minorran its pre-checks and prepared the version and changelog.Screenshots
N/A
Risk
Intent
release, depth standard. Release rangev0.23.0..origin/mainis the single commit 19520a2 (#56), which had an independent review with no findings. The bump hunks (version and changelog only) were checked in the principal session; no fresh reviewer was run on them. No breaking changes.How to revert
Revert the merge commit; never move or reuse the tag. Publish a follow-up patch if 0.24.0 is already on npm.
Deployment notes
After merge,
release-tag.ymltagsv0.24.0on the merge commit andpublish.ymlpublishes to npm, then creates the GitHub Release. Consumers (frontend) bump to 0.24.0 afterwards.