chore(release): 0.6.1#101
Merged
Merged
Conversation
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
1 participant
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
## [0.6.1] - 2026-05-04section toCHANGELOG.mdwith the deps bump (TypeScript 6, zod 4.4.3, lint chain) and theticket-add-viewdeflakeWhy a 0.6.1 right after 0.6.0
The 0.6.0 publish workflow fired on a tag pointing at the pre-fix commit and pushed the npm artifact before the deflake / dep bumps from PR #100 landed. npm's 72-hour version-reuse block means we can't republish 0.6.0 today — 0.6.1 is the clean re-ship. (Git tag
v0.6.0has been retargeted to the commit that's actually on npm so the registry and Git agree.)Test plan
pnpm typecheck·pnpm lint·pnpm test— green locally on TS 6 (231 files / 2217 tests)