Repository navigation
chore: release v0.9.26 - #7421
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
There was a problem hiding this comment.
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..54725d46contains exactly2927fe615(#7415),91ad7fb6e(#7419) and the release commit. The base is currentmain(91ad7fb6e). - Versions: all 20 JSON files change only
"version": "0.9.25"→"0.9.26", and no0.9.25remains in any JSON file at this head. - Notes:
docs/changelog.mdxandreleases/v0.9.26.mdmatch 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.
There was a problem hiding this comment.
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.
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.26onrelease/v0.9.26at main, with--fromthe v0.9.25 release commit because the box had no tags, then--no-tagfor 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
docs/changelog.mdxandreleases/v0.9.26.md, summary rewritten by hand (the generated one is a TODO)Not run: the release workflow and publish; I did not check that the compare link resolves before the tag exists.