Repository navigation
chore: release v0.9.1 - #6987
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
![heygengenesis[bot]](https://avatars.githubusercontent.com/in/2913576?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Verdict: APPROVE · 0 blocker · 0 important · 0 nits · head f36dacbc
Release scope matches main: v0.9.0..origin/main is exactly #6985 and #6986, and nothing has merged since the cut.
What I checked
- All 19 public manifests (16 packages plus 4 plugin/extension manifests) move 0.9.0 → 0.9.1, and no stale
0.9.0is left outside the notes. draft-changelog.ts 0.9.1 --from v0.9.0 --to origin/mainproduces the same bullets asreleases/v0.9.1.mdand the mdx<Update>block. Only the summary and the #6985 wording were edited by hand, and they match #6985's SAM/CDKIsPresent: falserule.- #6985 has no release prerequisites.
- CI is green on this head, including Release checks. The required test jobs were skipped as release-only.
— Claude (Genesis V2)
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Nov 2, 2026
jrusso1020
added a commit
that referenced
this pull request
Nov 2, 2026
…eaves the box 240px off seqplainkeys-none-center-r0-root-z100 failed 2 of 3 runs in the merge group for two version-bump PRs (#6970, #6987). In each failing undo the bytes come back but the box stays 240.42px off, which is a Studio undo race, not noise. It stays measured and listed; #6989 tracks the fix, which removes this entry. 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.
Release v0.9.1.
A Lambda render started straight on the state machine without a
PlanProtocolnow runs as Plan v2 instead of failing at its first step. The SDK and CLI always send"v2", so they were not affected.Changes since v0.9.0: #6985, #6986.
No visible change
This pull request is a version bump and the changelog only. Each change was captured in its own pull request.
Size
A release PR is a version bump and a changelog entry; it has no code to fold into another pull request.
🤖 Generated with Claude Code