Repository navigation
chore: release 0.23.0 - #55
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.23.0 of
@behindthemusictree/ui: shipsStepList(#54) so grow can show every step of a pipeline run.Changes
packages/ui/package.json: 0.22.0 → 0.23.0.CHANGELOG.md:[Unreleased]moved to[0.23.0] - 2026-11-12.v0.22.0..main: onlyStepList(additive).Test plan
pnpm release -- minor(runs the release validator),pnpm build,pnpm lint: pass.StepListtests ran and passed in feat(ui): add StepList primitive #54 (112 tests).Screenshots
N/A.
Risk
Intent
release, depthstandard. The release payload is the single additive component from #54, which already had an independent review with no findings; this PR only adds the version bump and changelog section, so no second full review. Minor bump, no breaking change.How to revert
Revert the merge, then ship a patch release; a published npm version cannot be unpublished.
Deployment notes
After merge,
release-tag.ymlcreates tagv0.23.0on the merge commit andpublish.ymlpublishes to npm and creates the GitHub Release. Target:main(GitHub flow, no back-merge).