Support Opus 5.5 and default image generation to Images 2.5 - #508
Merged
Merged
Conversation
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
1 participant
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.
Why
Expose the new models while keeping explicit older model choices and the Zod 3 / generated Zod 4 compatibility boundary.
Changes
Default image intents to
openai/gpt-image-2.5-flare, add optional Sunburst and Opus 5.5 capabilities, update CLI/help examples and release changeset.Validation
yarn check,verify:full, current wrapper/type parity, and packed CLI-default validation pass. Council completed with no findings. The optional historical 4.11 package fingerprint already differs from main 4.13.1; no old fingerprint was rewritten.Rollout
Do not publish before API2 #9187 is deployed and live generation/edit smokes pass. No npm publication or merge has occurred.
Model source: official Opus 5.5 migration guide. Image IDs and capabilities: OpenAI Images 2.5.
GitHub Action compatibility hold
Keep the existing action pin and Opus 5 model: the bundled CLI predates the required 2.1.280. The upstream 2.1.280/Agent SDK 0.3.280 candidate has green unit/type checks but failed live integration checks; released
v1still bundles 2.1.278. The failure is not proven unrelated. Only these workflows are held; supported application/native CLI paths use Opus 5.5. Parsed workflow semantics match main exactly; explanatory comments record the release gate.Final CI receipt
All hosted checks pass on
d125bfd0c664b2edbd53e22cfb7380b0b27a91c8, run 35779909476, attempt 2. The first Supabase Edge container exited 135 before producing output; one targeted retry passed. Node 20/22/24 units, E2E, verify fast/full, build, release dry run and Next.js image fixture all passed without retries. No runtime/SDK code changed after the earlier all-green502048dcandidate; the follow-up only preserves the original GitHub Action model pending upstream compatibility.Landing receipt
Squash-merged with explicitly authorized
--adminon 2026-09-22T21:43:18Z:b1fb7d3282a03dbcdb1976169c3bd337277a60a7. This supersedes the pre-merge status wording above. The tested PR head was d125bfd. Incoming green PR #507 adds server-owned ThumbHash Storage/Viewer behavior. Its only shared paths are two README files, with disjoint sections; both changes are retained. The squash tree exactly matches the inspected three-way merge.Only Git merges and local checkout restoration were requested. No manual production deployment, package publication, or service restart was performed; the API2-first live generation/edit/mask smoke gate remains.
Sister PRs