chore: release v0.8.1 - #3319
Merged
Merged
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
miguel-heygen
force-pushed
the
release/v0.8.1
branch
from
August 18, 2026 01:12
1f1fc3d to
fbd14cd
Compare
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
Release HyperFrames v0.8.1 from current
main.Why
#3316 is the one users will feel. A value picked with
--varswas dropped on the way to the filehyperframes addwrites, so the installed component rendered its defaults and nothing said otherwise. The same release fixes the catalog preview ignoring chosen values, and makes a failed install name the registry it could not reach and the actual reason.#3314 moves Studio's FFmpeg prompt to before an export rather than after one fails.
#3320 is what lets the preview half of #3316 arrive at all. The docs pinned the player CDN URL to a minor line and the pin had gone stale, so a published fix never reached the catalog pages. They ask for
latestnow, which means this release reaches the docs on its own once npm has it. jsDelivr serveslatestwith a twelve hour edge cache, so the pages pick it up within about that, not instantly.How
Prepared with the repository's stable release workflow, drafted from the
v0.8.0tag so the notes cover exactly what landed after it. This branch was rebuilt on top of currentmainafter #3320 merged, so the release commit sits on the same tree the publish workflow will build.The publish workflow will use the immutable merge SHA, create
v0.8.1, publish npm packages tolatest, and cut the GitHub release after this PR is approved and merged.Test plan
Validation completed locally on the rebuilt branch:
bun run test:scripts: 184 Node tests and 29 catalog Vitest tests passed.bunx oxfmt --check docs/changelog.mdx releases/v0.8.1.mdpassed.Not covered
Component catalog pages still will not answer their variables panel after this ships. That is a separate defect: their preview payload is built from a hand-copy of the snippet, and 166 of the 168 components declaring variables have a copy with the declaration missing, so there is nothing in the markup for a chosen value to reach. Blocks are unaffected and do respond.