Repository navigation
chore: release v0.9.24 - #7411
Closed
miguel-heygen wants to merge 1 commit into
Closed
miguel-heygen wants to merge 1 commit into
miguel-heygen wants to merge 1 commit into
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
Contributor
There was a problem hiding this comment.
Approving at a15d1863.
- Commit range: v0.9.23...head is exactly the four PRs listed (#7410, #7402, #7398, #7401) plus this release commit, and head sits directly on current
main. - Version bump: 20 manifests (15 packages and 5 plugin/extension) move from 0.9.23 to 0.9.24. No stale
0.9.23remains outside the changelogs, and no public manifest was missed. - Notes:
releases/v0.9.24.mdand thedocs/changelog.mdxentry match each other and link the correct commits and PRs. - CI: every workflow on this head is green (CI, Docs, CodeQL, regression, Windows render, Lambda image, player perf).
This is a release PR, not a fix PR, so a fails without the fix: line isn't required. The fixes it carries were gated in their own PRs.
Not covered here: the oss-release-gate desktop walk with the packed packages, which the body also lists as still open.
Merged
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
Release v0.9.24: version bump,
releases/v0.9.24.md, and the docs changelog. Merging publishes to npm.Why
Ships the seeded render: re-rendering a film with the same settings now gives the same result, because every render seeds its random values (#7410).
It also carries capture pages that load only the clips on screen (#7402), a
checkthat replays an unchanged project's last pass and takes--no-craft(#7398), and a CI change that installs ffmpeg through the GitHub API asset route (#7401).Related work
Follows v0.9.23 (#7399). Refs #7410, #7402, #7398, #7401.
What I measured
bun run release:prepare 0.9.24 --from <v0.9.23 commit>ran on currentmain(a remote Linux copy without tags): the first run drafted the notes, the summary is by hand with both notes markers removed, and the second run wrote the version bump with--no-tag, so no commit or tag was made by the script.releases/v0.9.24.md. The compare link is v0.9.23...v0.9.24.bun run format:checkexit 0.What I did NOT exercise
oss-release-gate).No visible change
Version bump and changelog only. Each change was captured in its own PR.