chore: release v0.8.14 - #3474
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.
What
Stable release v0.8.14. Version bumped across every package and plugin manifest,
releases/v0.8.14.mdadded, and the entry prepended todocs/changelog.mdx.Why
Two commits have landed since v0.8.13:
fix(skills,lint): agent skills taught composition rules the runtime does not enforce, four of which made a render fail outright (fix(skills,lint): correct composition-contract claims the code contradicts #3468).feat(cli):hyperframes addrecords installed catalog items inhyperframes.json, sorender_completecan report which catalog blocks a finished video actually used (feat(cli): report which catalog items a render actually used #3470).The second is the only user-visible file change: a project's
hyperframes.jsongains aregistryItemsarray after the nexthyperframes add. It is declared in the published config schema, so a schema-aware editor accepts it.How
bun run release:prepare 0.8.14, then the generated summary was rewritten and the TODO marker removed, then the same command again to set versions and create the release commit.One deviation worth naming: the commit needed
HF_MAX_NONLFS_KB=1024.docs/changelog.mdxhas grown to 512 KB, past the 500 KB pre-commit guard. That guard exists to keep large binaries out of the git pack, so it is firing on a text file the docs site renders, and the changelog crosses the line a little further every release. A separate PR fixes the guard rather than folding a repo-wide policy change into a release.Test plan
No code changes, so no tests were added. Verified by hand:
0.8.14, and nothing outside the release-allowed path set changed (the release script asserts this before committing).releases/v0.8.14.mdand thedocs/changelog.mdxentry carry a written summary, not the generated TODO marker.Tag
v0.8.14is deliberately not pushed yet. v0.8.13 is tagged on its merge commit, so this should merge with a merge commit and be tagged on main afterwards.