Repository navigation
Upgrade vendor SDKs and preserve runtime contracts - #63
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
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.
Upgrade all three vendor integrations to the latest stable PyPI releases observed on October 2, 2026, while preserving optional extras and Python 3.10 support.
Codex retains the 0.157.1 minimum required by native permission profiles, raises its upper bound to <0.161, and keeps the CLI exactly coupled to the SDK. Declarations, lockfile and compatibility manifest are updated together without release cooloffs.
Antigravity 0.1.20 removes directory/search tools from its default collections. Explicit read-only allowlists now continue to accept those three legacy tools without re-enabling them by default or admitting deprecated write tools. Claude exposes opt-in
verbatim_prompts=Truefor literal composed goals and refuses SDKs that cannot honor it; existing callers retain their current prompt behavior. Provider docs explain the initial-attachment tradeoff. The October integration review records the upstream changes and adapter decisions.Validation:
Claude and Antigravity were verified through local real-SDK configuration checks, not live provider tasks. Native binary internals remain opaque, and official Antigravity sources had no matching 0.1.20 release-note entry; exact published wheel sources and contract probes provide the inspected compatibility evidence.