Skip to content

require tunnel 0.1.10#748

Open
kcoopermiller wants to merge 1 commit into
mainfrom
improvement/require-tunnel-0.1.10
Open

require tunnel 0.1.10#748
kcoopermiller wants to merge 1 commit into
mainfrom
improvement/require-tunnel-0.1.10

Conversation

@kcoopermiller

@kcoopermiller kcoopermiller commented Jun 15, 2026

Copy link
Copy Markdown
Member

Note

Low Risk
Version pin bump only; no runtime or CLI logic changes in this diff.

Overview
Bumps the prime package’s minimum prime-tunnel dependency from >=0.1.9 to >=0.1.10 in pyproject.toml.

The dependency guard test in test_tunnel_cli.py is updated so installs must satisfy the new floor.

Reviewed by Cursor Bugbot for commit 43c00c7. Bugbot is set up for automated code reviews on this repo. Configure here.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 43c00c77ba

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

"prime-sandboxes>=0.2.27",
"prime-evals>=0.2.3",
"prime-tunnel>=0.1.9",
"prime-tunnel>=0.1.10",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Bump the workspace tunnel package too

When this repo is installed from the workspace, uv is configured to use the local prime-tunnel source and the root override still permits prime-tunnel>=0.1.6 (pyproject.toml:23). That local package is still version 0.1.9 (packages/prime-tunnel/src/prime_tunnel/__init__.py:3), so monorepo dev/test/release-e2e runs can continue exercising 0.1.9 even though the CLI now declares 0.1.10. If the CLI depends on fixes in 0.1.10, bump the workspace package/release metadata or stop resolving it from the local 0.1.9 source with this dependency change.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant