Skip to content

chore: release v0.8.187 - #6115

Merged
miguel-heygen merged 1 commit into
mainfrom
release/v0.8.187
Oct 23, 2026
Merged

miguel-heygen merged 1 commit into
mainfrom
release/v0.8.187

Conversation

@miguel-heygen

Copy link
Copy Markdown
Collaborator

Release v0.8.187: version bump to 0.8.187 in every package and plugin manifest, the release notes in releases/v0.8.187.md, and the matching entry in the docs changelog.

Merging this PR runs the Publish workflow, which creates the v0.8.187 tag at the merge commit, publishes the npm packages and creates the GitHub release. No tag is pushed by hand.

This is the first release that also builds the arm64 ffmpeg and attaches the arm64 video image to the GitHub release (from the Lambda arm64 work), so the Publish run is worth reading end to end.

No visible change

Version numbers and release notes only. No code changes in this PR.

@mintlify

mintlify Bot commented Oct 23, 2026 •

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
hyperframes 🟢 Ready View Preview Oct 23, 2026, 6:17 AM

💡 Tip: Enable Automations to automatically generate PRs for you.

@heygengenesis heygengenesis Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verdict: APPROVE · 0 blocker · 0 important · 0 nits · head c1ca44d1

Release bookkeeping checks out: 19 manifests go from 0.8.186 to 0.8.187, the release notes match the docs changelog entry line for line, and the notes cover every one of the 32 commits from v0.8.186 to 504ec2b30 exactly once.

Scope
  • The base is the current main tip (504ec2b30). The branch is release/v0.8.187, which is the name the Publish workflow keys on.
  • Only packages/sdk-playground (private: true) and the remotion test-corpus fixtures stay off 0.8.187, as they did in earlier releases.
  • CI was still running at review time, so branch protection gates the merge on it. The arm64 Publish steps can only be checked after the merge.

@github-actions

Copy link
Copy Markdown
Contributor

Edit accuracy: accurate 271 (base branch 271), smooth 128 of those

The gate passes.
Smoothness is reported in the artifact, not gated. A case fails only if it fails 2 of 3 runs.

Quarantined, measured but not gated (0)

Unstable (1)

  • seqplainkeys-none-px-r0-root-z100: tracking 0.06, pressJump 0, drop 0, reload 0, render 0.03, renderKey -, undo false, teleport true / tracking 0.06, pressJump 0, drop 0, reload 0, render 0.03, renderKey -, undo true, teleport true / tracking 0.06, pressJump 0, drop 0, reload 0, render 0.03, renderKey -, undo true, teleport true

@miguel-heygen
miguel-heygen added this pull request to the merge queue Oct 23, 2026
Merged via the queue into main with commit 6fe8306 Oct 23, 2026
89 checks passed
@miguel-heygen
miguel-heygen deleted the release/v0.8.187 branch October 23, 2026 06:50
@heygengenesis heygengenesis Bot mentioned this pull request Oct 23, 2026

This branch had an error being deployed

1 failed and 1 active deployments
npm-publish — c1ca44d1 Deployed Oct 23, 2026 by miguel-heygen via Publish #4746
staging - docs — c1ca44d1 Deployed Oct 23, 2026 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant