chore: release v0.8.6 - #3386
Conversation
miguel-heygen
left a comment
There was a problem hiding this comment.
Reviewed exact release head beeece5212fe95b8167a297f0787097f5c1e9654.
The release tree and publication contract are internally consistent:
v0.8.5..HEADcontains exactly the five advertised merge commits plus this release commit; every changelog link resolves to the corresponding merge SHA.- All 13 packages enumerated by
set-version.tsand all three plugin manifests are0.8.6. The publish workflow covers the same 13 npm artifacts (12 scoped packages plus the unscoped CLI rewrite). Neither remotev0.8.6nor any npm0.8.6artifact exists, so the tag/version namespace is free. - The two constituents that lacked an APPROVED aggregate were audited at their merged heads: #3382's follow-up adds the mounted
isPlaying: truehook regression and corrects the store-clock wording flagged in its prior review; #3385 removes onlyhead_leaked_textplus its private helpers/patterns/fixtures, whilevisible_markup_commentand its coverage remain intact. The other three constituents are approved and match the release notes. - The exact-head required
Buildjob includes—and passed—both the monorepo build andverify:packed-manifests; Linux/Windows tests, runtime contract, typecheck, Windows render, regression, docs, format, and CodeQL are green.
Audited: all 18 release-file diffs; package/plugin version parity; release range and changelog SHAs; publish workflow/package mapping; remote tag + npm collision checks; final #3382/#3385 source/test deltas; required CI job steps.
Trusting: compiled artifact bytes beyond the successful packed-manifest/clean-consumer verifier; implementation bodies of #3295/#3380/#3383 under their separate exact-head reviews.
Verdict: APPROVE
Reasoning: The release contains exactly the documented fixes, versions and publish targets are synchronized with no namespace collision, previously unstamped constituents hold at their merged heads, and every required release/consumer gate is green.
— Magi
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
What
Prepare the stable HyperFrames v0.8.6 patch release.
release/v*merge workflow. No stable tag was pushed from this branch.Why
This patch ships two user-visible audio correctness fixes: ended dialogue now replays after backward timeline seeks, and delayed render-mix clips stay at their authored times instead of jumping to the start or disappearing.
It also keeps subcomposition timelines open during playback, requires confirmation before skill updates, and removes a brittle lint rule that could block correct compositions.
Included changes
head_leaked_textlint ruleValidation
mainhead and the local-onlyv0.8.6tag points to the exact release commitMerging this reviewed PR will create the stable tag at the immutable merge commit, publish npm packages with the
latestdist-tag, and create the GitHub release.