Repository navigation
chore: release v0.9.3 - #7010
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
![heygengenesis[bot]](https://avatars.githubusercontent.com/in/2913576?s=60&v=4){kind=small}
There was a problem hiding this comment.
Requesting changes at 98c3f104.
Blocker: v0.9.3 would ship a change that its release notes leave out.
This branch forks from c54f84859 (#7002). Since then, main has gained d17b95831, feat(studio-server): stamp a project hf-ids without holding the event loop (#7004), merged 2026-11-02T11:30:17Z. publish.yml tags and publishes merge_commit_sha, and that commit sits on top of current main. So the published v0.9.3 packages (@hyperframes/studio-server at least) would contain #7004. But docs/changelog.mdx, releases/v0.9.3.md and the PR body ("Changes since v0.9.2: #7002, #6997, #6998, #6996, #6999") don't mention it. The "View the full commit range" link would show it, which contradicts the notes.
v0.9.2 didn't have this gap: every PR in v0.9.1..v0.9.2 is in its release notes. Please rebase release/v0.9.3 on current main and regenerate the entry with bun run changelog:draft 0.9.3 --write, so it lists #7004. Alternatively, hold #7004 back explicitly.
Verified otherwise:
- The bump is complete. The same 21 files change as in the v0.9.2 release, and no
"version": "0.9.2"remains in a manifest. - The 5 listed PRs and their commit SHAs match
v0.9.2..c54f84859exactly. - The version and changelog files are the only changes. There's no code.
- This isn't a fix PR, so the
fails without the fix:rule doesn't apply.
98c3f10 to
a5ea45d
Compare
There was a problem hiding this comment.
Approving at a5ea45df. The blocker from my previous review is resolved.
- The branch now sits on current
main(d17b95831), with nothing onmainpast it. Every PR inv0.9.2..d17b95831(#7004, #7002, #6997, #6998, #6996, #6999) appears in bothdocs/changelog.mdxandreleases/v0.9.3.md, with matching commit SHAs. #7004 is listed under Features. - It's a version bump only: the same 21 files as the v0.9.2 release, 19
"version": "0.9.2"→"0.9.3"lines, and none left at 0.9.2. There are no code changes. - This isn't a fix PR, so the
fails without the fix:rule doesn't apply.
CI is still running on this head. The Actions runs marked cancelled were replaced by newer runs on the same head.
GitHub Actions
Failure
GitHub Actions
Inactive
Release v0.9.3.
Stamping a project's ids no longer holds up the Studio host, and long media clips no longer leave it unanswered. A preview reload writes the composition as it is now. Measure and diff say why they failed.
Changes since v0.9.2: #7004, #7002, #6997, #6998, #6996, #6999.
No visible change
This pull request is a version bump and the changelog only. Each change was captured in its own pull request.
Size
A release PR is a version bump and a changelog entry; it has no code to fold into another pull request.