Skip to content

chore: release v0.9.26 - #7421

Merged
miguel-heygen merged 1 commit into
mainfrom
release/v0.9.26
Nov 8, 2026
Merged

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

Conversation

@miguel-heygen

@miguel-heygen miguel-heygen commented Nov 8, 2026 •

Copy link
Copy Markdown
Collaborator

What

Release v0.9.26: a version bump of all packages and plugin manifests, the changelog entry and releases/v0.9.26.md.

It carries two changes since v0.9.25 and nothing else:

Why

Ships those two fixes.

Related work

Follows chore: release v0.9.25 (#7414).

How

bun run release:prepare 0.9.26 on release/v0.9.26 at main, with --from the v0.9.25 release commit because the box had no tags, then --no-tag for the bump with the notes already reviewed. No tag is pushed; the release workflow tags when this PR closes. The diff is 22 files: 20 version strings, the changelog entry and the notes file, the same shape as v0.9.25.

No visible change

Version bump and changelog only. Each change was captured in its own PR.

Test plan

  • Unit tests added/updated (release commit only, no code)
  • Manual testing performed: diff checked to be only version strings plus the two notes files
  • Documentation updated: docs/changelog.mdx and releases/v0.9.26.md, summary rewritten by hand (the generated one is a TODO)
  • Comments follow CONTRIBUTING.md "Comments"

Not run: the release workflow and publish; I did not check that the compare link resolves before the tag exists.

@mintlify

mintlify Bot commented Nov 8, 2026 •

Copy link
Copy Markdown

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

Project Status Preview Updated
hyperframes 🟢 Ready View Preview Nov 8, 2026, 11:26 PM

💡 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.

Requesting changes at 54725d46. The release content is right, but a required check fails.

Blocker: Studio and player captures (required on main) fails. The release bumps packages/studio/package.json and packages/player/package.json, so the check needs a ## Before / ## After section or a ## No visible change section in the body, and this body has neither. The v0.9.25 release passed by adding:

## No visible change

Version bump and changelog only. Each change was captured in its own PR.

Add that to the body (edit the text, no attachments needed) and re-run the job. That body edit is the only change needed.

Checked and OK

  • Scope: v0.9.25..54725d46 contains exactly 2927fe615 (#7415), 91ad7fb6e (#7419) and the release commit. The base is current main (91ad7fb6e).
  • Versions: all 20 JSON files change only "version": "0.9.25" → "0.9.26", and no 0.9.25 remains in any JSON file at this head.
  • Notes: docs/changelog.mdx and releases/v0.9.26.md match each other, list both PRs with the correct commit links, and file them under Fixes (#7419) and Performance (#7415).

CI, CodeQL, Docs and the Lambda image were still running when I posted this.

@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.

Approving at 54725d46 (same head as my last review). The blocker is resolved: the body now has a ## No visible change section, and the newest PR captures runs on this head pass (23:26:19Z and 23:30:03Z). The code diff hasn't changed, so my earlier checks still apply:

  • the scope is #7415 and #7419 only;
  • all 20 JSON version fields go from 0.9.25 to 0.9.26;
  • the two changelog files match.

On this head, CI has one completed run that succeeded and one still running, and CodeQL is still running.

@miguel-heygen
miguel-heygen added this pull request to the merge queue Nov 8, 2026
Merged via the queue into main with commit 0c6c7fc Nov 8, 2026
127 of 129 checks passed
@miguel-heygen
miguel-heygen deleted the release/v0.9.26 branch November 8, 2026 23:54
@miguel-heygen miguel-heygen mentioned this pull request Nov 9, 2026
3 of 4 tasks

This branch was successfully deployed

2 active deployments
npm-publish — 54725d46 Deployed Nov 8, 2026 by miguel-heygen via Publish #5988
staging - docs — 54725d46 Deployed Nov 8, 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