Upgrade SDK integrations and complete the PR workflow - #59
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.
Upgrade requests previously stopped at evidence reports or dependency updates, leaving adapter changes and PR publication as separate steps. The canonical skill now carries an upgrade through upstream impact analysis, required source adaptations, verification, and a regular PR; explicit report-only and local-only requests keep their narrower scope.
This upgrade also fixes Antigravity authentication:
AntigravityAgentRuntime(vertex=True, api_key=...)now preserves Vertex Express endpoint selection instead of discardingvertexand selecting Gemini. It rejects older or unverifiable SDK releases and mixed explicit project/location credentials and refuses SDK configurations that would drop the requested endpoint. Real SDK constructor tests cover both Gemini and Vertex with conflicting ambient settings, without making provider requests.claude-agent-sdkgoogle-antigravityopenai-codexopenai-codex-cli-binThe Codex SDK requires CLI 0.147.0 exactly, so standalone CLI 0.149.0 is excluded from the package upgrade. Antigravity's new model default is inherited and documented, and its move toward turn-level usage is already supported. Lightweight presets and stop-continuation hooks change tool access or execution policy and are not applied implicitly.
The evolution collector now associates a release discussion's title with its body. This fixes missing evidence for the Antigravity 0.1.16 announcement, whose version appears only in the title, while rejecting unrelated navigation and longer version prefixes, prereleases, and local-version suffixes.
Validation: exact baseline/candidate API and behavior gates pass, and both release intervals have matching primary-source notes. Real Claude option construction passes on 0.2.148 and 0.2.152; real Antigravity endpoint checks pass on 0.1.15 and 0.1.16, retaining Gemini and refusing unsupported Express on the older SDK. The final Python 3.10 environment contains all four locked SDK packages: Ruff, strict mypy, lock validation, and pytest pass (542 passed, 3 live-provider smoke tests skipped; 90.39% coverage). The skill validator and existing workflow documentation tests also pass.
The final cumulative implementation review passed after both identified gaps were reproduced and fixed.
CI passed all ten applicable jobs on
f4485a2, including Python 3.10–3.13 core/all-SDK matrices, a fresh pip install, and the declared dependency floors.