Release CLI beta 38 - #346
Merged
Merged
Conversation
Ships the default-allow transparent mitmproxy egress gateway + account-level managed provider key handling merged in #345. beta.37 predates that merge, so v2 hosted runtimes tracking the clawdi@beta dist-tag need a new beta to pick up the gateway at runtime (the image stays stable; the CLI is runtime-installed). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Bumps
clawdi0.12.10-beta.37 → beta.38 to publish the default-allow transparent mitmproxy egress gateway + account-level managed provider key handling landed in #345.Why: v2 hosted runtimes install the full CLI at runtime tracking the
clawdi@betadist-tag (the image is a stable clean base and does not bake the CLI). beta.37 predates the #345 merge, so a new beta is required for runtimes to self-upgrade and activate the gateway. No image rebuild, no pod/manifest change.Rollout: merge →
cli-publish.ymlauto-publishes beta.38 under thebetatag → dev/canary v2 pods self-upgrade → validate gateway e2e on a dev CVM before any production rollout.🤖 Generated with Claude Code