Repository navigation
chore: release v0.9.62 - #8075
Merged
Merged
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
miguel-heygen
force-pushed
the
release/v0.9.62
branch
from
November 17, 2026 13:57
12a5889 to
026a951
Compare
jrusso1020
approved these changes
Nov 17, 2026
jrusso1020
left a comment
Collaborator
There was a problem hiding this comment.
Release 0.9.62 at 026a951: clean.
- Versions: all 15 publishable packages are at 0.9.62.
sdk-playgroundis private and stays at 0.6.106. The 5 plugin and extension manifests are bumped too. Internal dependencies useworkspace:ranges. There are no stray 0.9.61 strings outside test fixtures and the old notes. - Diff: one commit, 22 files, covering versions,
docs/changelog.mdxandreleases/v0.9.62.mdonly. There are no code changes, and the base (df31ce2b) is current main. - Contents:
df31ce2b(#8072) is an ancestor and listed in the notes. #8025 shipped in v0.9.61 and is correctly not repeated. All 11 commits inv0.9.61..df31ce2bare linked, including #8069, which was the Release checks failure at 12a5889. Release checks now passes. - Publish: the OIDC-only publish workflow is already on main via #8070, not in this PR.
- The
publishjob runs in thenpm-publishenvironment withid-token: write, and the workflow default ispermissions: {}. NODE_AUTH_TOKEN: ""leaves npm only the OIDC token, and there is no NPM_TOKEN path anywhere.- Triggers are push to main and
v*tags only. There is nopull_request_target, and every action is pinned to a SHA.
- The
- Signatures: the commit is signed.
Need from author: nothing.
— Rames
This branch was successfully deployed
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.
What
Releases HyperFrames v0.9.62: the version bump across the published packages and plugin manifests, and its notes in
releases/v0.9.62.mdanddocs/changelog.mdx. It is the first release published with npm trusted publishing alone (#8070): the publish step holds no stored npm token.No visible change
Version bump and changelog only. Each change below was reviewed, and where it shows, captured, in its own pull request.
Notes
Released on 2026-11-17.
Studio's sealed preview shows audio meters and audio groups, a layer reorder is one undo step again, and the engine checks still frames on several pages at once so text films start sooner. npm packages now publish with trusted publishing alone.
Features
Performance
Fixes
Internal
Full changelog
v0.9.61...v0.9.62