Skip to content

chore(cli): update opentunnel client - #57287

Merged
rekram1-node merged 1 commit into
devfrom
opentunnel-client-update
Oct 21, 2026
Merged

rekram1-node merged 1 commit into
devfrom
opentunnel-client-update

Conversation

@rekram1-node

Copy link
Copy Markdown
Contributor

Issue for this PR

No linked issue.

Type of change

  • Bug fix
  • New feature
  • Refactor / code improvement
  • Documentation

What does this PR do?

Problem: The pinned tunnel client predates its advertised connection limit check.

Change: Update the CLI dependency and lockfile to the 0.4.1 patch release:

- @opentunnel/client 0.4.0
+ @opentunnel/client 0.4.1

The transitive protocol package follows at 0.4.1. Out of scope: No relay or other remote-access changes.

How did you verify your code works?

  • bun install --frozen-lockfile --ignore-scripts
  • bun typecheck in packages/cli
  • bun run check (passed; existing lint warnings)
  • SDK import and plain route-validation smoke check

No listener-binding integration tests were run.

Screenshots / recordings

N/A

Checklist

  • I have tested my changes locally
  • I have not included unrelated changes in this PR

@opencode-agent opencode-agent Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The dependency bump does what it says. I ran the tunnel client from each checkout against a local fake relay that sends 260 open frames. On the base (0.4.0) all 260 connections opened. With this PR (0.4.1), 256 opened and the extra 4 were reset with too_many_connections. Apart from the version numbers, the only differences between the installed packages are that guard and the new error code. Reset codes are plain strings in the protocol, so relays that don't know the new code still accept it. In packages/cli, test/service.test.ts and bun typecheck pass, and remote-tunnel.ts needs no changes.

Public API: unchanged.

No concerns.

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