Skip to content

chore: release v0.8.188 - #6122

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

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

Conversation

@miguel-heygen

Copy link
Copy Markdown
Collaborator

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

v0.8.187 never reached npm: its publish job stopped on the package size budget for @hyperframes/aws-lambda (fixed in #6118). Nothing was released under that version, so its notes and changelog entry are folded into this release and the 0.8.187 entry is removed.

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

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, 9:38 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 8e2a1706

The 19 manifests go from 0.8.187 to 0.8.188. The notes are renamed to v0.8.188.md and match the docs entry. They add the 5 commits since the v0.8.187 tag (#6113, #6116, #6117, #6118, #6119), and the compare link now runs from v0.8.186 to v0.8.188. Nothing reached npm under 0.8.187 (checked hyperframes, cli, aws-lambda, engine and producer), so skipping that version is safe.

Scope

FYI, not gating: the failed publish left a v0.8.187 tag at the #6115 merge with no GitHub release. The branch is release/v0.8.188, the base is the current main tip (401d0655f), and CI was still running at review time.

@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 — 0 resolved, 0 open, 0 new · 8e2a1706 → ffda8cc9

Rebased onto c4c1e621d. The only content change adds the #6121 line to both the release notes and the docs changelog. The notes now cover all 6 commits since the v0.8.187 tag. Otherwise the diff is still only the 19 version bumps.

@github-actions

Copy link
Copy Markdown
Contributor

Edit accuracy: accurate 271 (base branch 271), smooth 143 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)

  • seqheldtwice-tlhold-px-r0-nested-z100: tracking 120.29, pressJump 312.3, drop 0.07, reload 0.07, render 0.03, renderKey -, undo true, teleport false / tracking 0.41, pressJump 0.11, drop 0.39, reload 0.39, render 0.02, renderKey -, undo true, teleport true / tracking 0.41, pressJump 0.11, drop 0.39, reload 0.39, render 0.02, 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 3badc9b Oct 23, 2026
88 checks passed
@miguel-heygen
miguel-heygen deleted the release/v0.8.188 branch October 23, 2026 10:13

This branch was successfully deployed

2 active deployments
npm-publish — ffda8cc9 Deployed Oct 23, 2026 by miguel-heygen via Publish #4753
staging - docs — ffda8cc9 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