Skip to content

wiretap v0.2.9

Choose a tag to compare

View all tags
@plutack plutack released this 11 Sep 06:25
· 48 commits to main since this release
v0.2.9
446b699
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

wiretap v0.2.9

This release makes transforms portable and brings privileged relay identity
management into the desktop GUI.

Relay server management

Settings now separates ordinary desktop configuration from a privileged
Relay server workspace. Relay operators can:

  • Connect using a relay URL and an admin token held in memory only.
  • Inspect relay health, version, connected desktop sessions, clients, and
    project ownership.
  • Create credentials for another client without replacing the registration
    used by the current desktop.
  • Revoke a client after a warning that its project bindings and queued relay
    webhook history will be deleted.
  • Move a project to another registered client while preserving the project's
    queued webhook history.

Client and project inventories display totals and use bounded scrolling for
larger installations. The Clients and Create client panels keep equal heights
at wide desktop sizes and collapse into a single column on narrower windows.

New client tokens are shown once for copying and are not written to the local
configuration. Leaving the Relay server workspace clears its admin token and
server snapshot from GUI memory.

The relay /health response now reports unique connected desktop tunnel
sessions. Upgrade wiretap-relay to v0.2.9 for an accurate Live tunnels
value. The other management controls use the admin APIs available since
v0.2.5.

Portable transforms

Transforms can now be exported and imported as strict, versioned JSON files.
The portable file includes the transform name, trigger, priority, enabled
state, and JavaScript program while excluding database IDs and timestamps.

Imports are limited to 1 MiB and reject unknown fields, unsupported versions,
missing names, invalid triggers, and trailing JSON. An imported transform opens
as an unsaved draft so it can be inspected and tested before persistence or
execution.

The transform editor also adds Duplicate. It copies the live program,
trigger, priority, and sample request into a disabled, unsaved draft. This
makes it safe to branch an existing transform without modifying the original.

Compatibility and upgrades

  • No relay database migration or storage-schema change is required.
  • The relay still assigns one owning client to each project. Multi-subscriber
    delivery and per-subscriber cursors are not part of this release.
  • Existing clients, tokens, project assignments, local captures, and relay
    webhook history remain compatible.
  • Transform files are a new optional workflow and do not alter transforms
    already stored in the local database.

Quality

The release includes GUI binding tests for relay administration and credential
isolation, relay health and unique-session coverage, strict transform-file
validation tests, frontend syntax checks, race-enabled tests across the
affected relay and GUI packages, production-equivalent GUI builds, and visual
review of empty and populated relay-management states.

Full changelog: v0.2.8...v0.2.9

Assets 10
Loading