chore: release v0.8.9 - #3422
Merged
Merged
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
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.
Stable release. Merging this PR publishes — the workflow checks out the merge SHA, verifies it, creates the
v0.8.9tag there, publishes the npm packages, and cuts the GitHub release usingreleases/v0.8.9.mdas its body.I stopped at opening the PR deliberately: the publish is the irreversible step and the process puts it behind a human merge.
What ships
Seven commits since
v0.8.8, all already reviewed and merged tomain.Release notes are rewritten for users rather than left as commit subjects, per
docs/contributing/changelog-process.mdx.releases/v0.8.9.mdand thedocs/changelog.mdx<Update>entry are in sync.Version
0.8.9, a patch bump, consistent withv0.8.8— which also carried a Features section. Say so and I will redo it as0.9.0if the psnr preflight is considered feature-weight enough to deserve a minor.Checks run locally
bun run verify:packed-manifests— 122 packed exports resolved, 117 executed, clean packed-consumer install, Node execution, TypeScript/Vite resolution, and CLI startup all verified.validate-release-channelsimulated with the merged-PR inputs (VERSION=0.8.9 DIST_TAG=latest EVENT_NAME=pull_request PR_HEAD_REF=release/v0.8.9) — validated forlatest.mint validateandmint broken-links— the new changelog entry renders and its links to the new audio pages resolve.0.8.9.v0.8.9tag was not pushed.One thing to decide, separately from this release
The release commit needed
HF_MAX_NONLFS_KB=600to get past thelargefilespre-commit hook.docs/changelog.mdxhas grown to 502 KB and the guard's default limit is 500 KB, so every future release trips this.The guard is explicitly aimed at binaries — its own header names ONNX models and MP4s — and
changelog.mdxis text that Mintlify has to read, so routing it through LFS would break the docs site. It needs one of: archiving older entries to a second page, exempting that path in the hook, or raising the default. That is a maintenance decision rather than something to slip into a release commit, so I have left it and am flagging it here.Not in this release: #3421, which is open and unreviewed.