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.
Studio self-updates currently reject a valid release when its AgentKit CLI pin differs from the running Studio's pin, failing during bundle extraction with
AgentKit CLI archive checksum is invalid. Thin bundles hit the same mismatch before falling back to a full bundle that also fails.The updater now reads the target VeADK wheel's literal Linux/x64 CLI contract using bounded AST parsing, without importing downloaded code. It checks full archives and thin runtime manifests against that target pin after the existing release size/SHA verification. Publisher build calls retain their fixed source pin. Missing, dynamic, ambiguous, oversized, or mismatched target contracts fail closed.
Cross-version regressions cover two historical installed pins, both providers, full/thin updates, artifact-probe fallback, release digest/size failures, and target wheel/CLI mismatch. The regression file runs in both mandatory release gates; every workflow Python command remains pinned to the frozen environment.
Validation: the original main implementation fails 24 regression cases; all 204 related tests pass on Python 3.12, including 28 new cross-version and gate cases. Ruff, Pyright (zero errors), pre-commit with secret scanning, and workflow shell syntax checks pass. Existing installations need one control-plane deployment of the corrected updater before subsequent in-product updates can cross CLI versions. A Release Server-only rollout cannot replace an already installed validator. Online recovery has not been performed in this change.