Repository navigation
docs(release): list #4330 in the v0.8.71 release notes - #4400
Closed
vanceingalls wants to merge 1 commit into
Closed
vanceingalls wants to merge 1 commit into
vanceingalls wants to merge 1 commit into
Conversation
The v0.8.71 release PR (#4395) was cut from d1048cf, but #4330 merged onto main before it, so the squash commit the tag points at — and the packages the publish workflow built from the merge ref — include the data-vfx-chain backdrop capture and the luma-matte/noise kernels. The generated notes never saw that commit. Add it under Features in both notes files, extend the summary sentence, and put Runtime in the docs entry's tags the way the generator would have. Co-Authored-By: Claude Fable 5.1 <[email protected]>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
2 of 3 tasks
Contributor
|
This PR has had no activity for 14 days, so it is marked stale and will close in 7 days. Push a commit or leave a comment to keep it open. A maintainer can add |
Collaborator
|
Closing under the new stale policy (no activity for 3+ weeks), so the work is free for someone else to pick up. Reopen it, or open a new PR, whenever you pick it back up. |
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.
The v0.8.71 release PR (#4395) was prepared from base d1048cf. #4330 (data-vfx-chain backdrop capture, luma-matte and noise kernels) merged to main at 84e36fc before #4395 did, so the
v0.8.71tag (58c873d) has it as a parent and the published packages include it — but the generated release notes never listed it.This PR only edits
releases/v0.8.71.mdand the v0.8.71 entry indocs/changelog.mdx: a## Featuressection with the #4330 bullet, one extra sentence in the summary, andRuntimein the docs entry's tags (the generator's rule isRelease+ the first three scopes, newest commit first). No version, package or code change; nothing is republished. I'll mirror the same text into the GitHub Release body once the publish run has created it.What I did NOT exercise
Nothing to run — release metadata text only.
🤖 Generated with Claude Code