Repository navigation
chore: release v0.9.8 - #7077
Merged
Merged
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.
Approved at ec623333. No blockers found.
- The diff is a release only: 0.9.7 → 0.9.8 in the 15 published
packages/*and the 5 plugin/extension manifests (the same 21 files as v0.9.7 in #7064), plus thedocs/changelog.mdxentry andreleases/v0.9.8.md. No source changes. The private packages (root, sdk-playground, studio/frontend) are correctly left alone. - The release range is complete.
v0.9.7...ec623333holds exactly #7046, #7067, #7066, #7070 and #7041, plus this commit. Every one is merged, each appears in the changelog under the right section with the right merge SHA, and the branch is 0 commits behindmain. - CI is green at this head: CI, Docs, CodeQL, Lambda arm64 image, regression, preview-regression, Windows render, PR captures and Player perf/Safari perf.
- This isn't a fix PR, so the "fails without the fix" rule doesn't apply.
Nit (not blocking): the #7046 line ("Reverse on Free runs billing subscribe credited to the run") reads awkwardly as user-facing release notes.
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Nov 3, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Nov 3, 2026
miguel-heygen
temporarily deployed
to
npm-publish
November 3, 2026 09:39 — with
GitHub Actions
Inactive
SanHsien
added a commit
to SanHsien/hyperframes
that referenced
this pull request
Nov 4, 2026
…r long runs Ports upstream heygen-com#7087 (fc006f7): the finished-job TTL now counts from when a sweep first sees the job finished, not from createdAt, so a render that ran longer than the TTL is still readable after it completes. Adds the shared helper and its regression tests, which failed on the old code with 404. Also records the fourth 2026-11-04 upstream review pass: watermark advanced to 3f42dc1 / PR heygen-com#7077 with file:line evidence; the remaining range stays in ROADMAP. Co-authored-by: Miguel Ángel <miguel.sierra@heygen.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.8: version bump across the packages and the changelog for v0.9.8.
Why
Ships the producer changes that let renders fall back to screenshot capture: #7066 (a render request can force screenshot capture) and #7070 (a BeginFrame capture failure re-renders on a screenshot session), plus #7041, #7067 and #7046.
No visible change
Version bump and changelog only. Each change was reviewed and captured in its own PR.
Test plan
bun run release:prepare 0.9.8passed after the summary was written and the drafting markers removed.