Repository navigation
chore: release v0.8.223 - #6869
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
There was a problem hiding this comment.
Verdict: APPROVE · 0 blocker · 0 important · 0 nits · head c127a721
The release notes match draft-changelog.ts 0.8.223 --from v0.8.222 bullet for bullet (14 PRs, #6841–#6860), and main has nothing past the release base. #6833's merge condition holds: hyperframes.studio/pricing, /pricing?from=cli and /plan all return 200 on prod.
Scope
Every non-private packages/* is bumped to 0.8.223 (only the private sdk-playground isn't), and so are the 5 plugin manifests. The mdx <Update> block matches releases/v0.8.223.md. No CLI source references the 404ing /account/plan any more. All 11 Actions runs at this head passed (Comments skipped).
What
Release v0.8.223: version bump on all packages and plugin manifests, plus the drafted changelog (
releases/v0.8.223.md,docs/changelog.mdx).Why
v0.8.222 does not include #6833, which lets the CLI's reverse-any-video skill run on the HyperFrames plan and points
billing subscribeat the live pricing page. That page is live in production now, so the CLI can ship it.No visible change
Version bump and changelog only. Each change in the notes was captured in its own PR.
Related work
Notes cover every merge since v0.8.222, v0.8.222...v0.8.223. PRs still in the queue ride the next release.
How
bun run release:prepare 0.8.223on a branch from main. The summary replaces the generated TODO and the style-bar line is removed in both files. The local tag the script made was deleted; the publish workflow tags the merge.Size
21 files, 90 added lines, all version strings and changelog text.
Test plan
release:preparere-ran clean after the summary was written. CI Build uploads the release tarballs for the gate.What I did NOT execute
No publish or tag. Merging this PR publishes.