Skip to content

v0.1.6 new clients contract

Choose a tag to compare

@LEADBERG-studio LEADBERG-studio released this 25 Jul 07:13
· 23 commits to main since this release

Tunnellio v0.1.6

Summary

  • This release aligns the client with the new Tunnellio discovery, auth, and session contract.
  • The client now reflects the server's final auth/connection contract, supports OAuth discovery helpers, and keeps richer runtime/session metadata.
  • Release validation included local source checks, the expanded manual suite, and live plan/session verification against test.tunnellio.site.

Highlights

  • Added OAuth discovery helpers and PKCE utilities.
  • Added session-aware runtime handling for open, heartbeat, resume, close, and complete flows.
  • Added resume-token aware heartbeat/close handling and richer runtime snapshot metadata.
  • Expanded config, planner, tests, and documentation for the new server contract.

Artifacts

  • tunnellio.exe — standalone Windows binary
  • tunnellio-source-v0.1.6.zip — universal Python/source archive

Usage notes

  • The server remains the source of truth for the final authMode and connectionMode; callers should read the returned runtime snapshot instead of assuming requested modes were granted unchanged.
  • For random or ephemeral domains, launch with a runtime name and then call show-config --name <runtime> to read back the final server-side hostname and public URL.
  • The ready binary is Windows-specific; the source archive is the portable project package for Python/OpenSSH environments.

Changelog

  • Aligned the client with the new discovery, auth, and session contract.
  • Added OAuth discovery helpers, PKCE utilities, and extended session-aware planning/runtime metadata.
  • Added live-validated session lifecycle handling with resume-token aware heartbeat, resume, and close calls.
  • Expanded config, runtime snapshots, tests, and docs for the new server contract.

Notes for GitHub publication

  • Upload both tunnellio.exe and tunnellio-source-v0.1.6.zip from this folder.
  • Reuse this Markdown as the GitHub release body.
  • Publish the release from the main commit for v0.1.6 after creating the GitHub release.