[kcoopermiller]

Summary

Bumps prime-tunnel from 0.1.15 to 0.1.16. Merging to main tags prime-tunnel-v0.1.16 and publishes to PyPI.

What's in this release

• feature(tunnel): add Tunnel.keep_serving() to keep a tunnel serving #1053: adds Tunnel.keep_serving(health_path), a coroutine the caller runs as a task. It checks the tunnel through its public URL and restarts frpc under the same URL when the tunnel stops serving. It raises TunnelGoneError when the registration is gone and ends when the tunnel is stopped.

This adds to the API and changes nothing for existing callers. Nothing calls keep_serving until a caller adopts it.

No other changes to packages/prime-tunnel since 0.1.15.

Testing

• pytest packages/prime-tunnel on this branch: 100 passed.
• uv lock --check passes.
• feature(tunnel): add Tunnel.keep_serving() to keep a tunnel serving #1053's live results are in that PR. It wasn't tested live against the case it's mainly for: frpc connected and not frozen, but not serving. A frozen frpc is the closest test.

🤖 Generated with Claude Code

---

Note

Low Risk
The diff is a single version string change with no runtime logic; publish risk is limited to packaging/tagging the existing 0.1.16 tree.

Overview
Release bump only: updates __version__ in prime_tunnel from 0.1.15 to 0.1.16 so merging to main can tag prime-tunnel-v0.1.16 and publish to PyPI.

There are no other code changes in this diff. The 0.1.16 artifact includes the already-merged Tunnel.keep_serving(health_path) API from #1053; this PR does not modify that behavior.

^{Reviewed by Cursor Bugbot for commit 7a21ce5. Bugbot is set up for automated code reviews on this repo. Configure here.}

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-11-02T17:34:17.037514Z	7a21ce5	PR opened

ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.