Skip to main content

​
Updates

Data Relay Link separates project updates from upstream Data Relay Link binary updates.

​
Update decision flow

​
Project update

Check first:
Then update:
A normal supported project update is designed to preserve:
  • CLIENT ID and client management identity
  • project private CA
  • Data Relay Link token
  • registry state
  • enrollment state where applicable
  • service definitions
  • persistent public service-port reservations
A normal update is not a re-enrollment operation.

​
Stable release vs development main

Do not copy a development-only command into stable field documentation unless the operator explicitly opted into development behavior.
show upstream is informational. Data Relay Link does not automatically install the newest upstream Data Relay Link release. The current stable release remains pinned to the qualified version, v0.71.0.

​
Same-version refreshes

Update decisions are not based only on the visible project version string. Verified release metadata and bundle SHA256 can distinguish changed builds even when the project version text is unchanged.

​
After any update

Then test at least one representative published service through its public endpoint.
Do not manually replace the bundled relay-server/client runtimes with arbitrary newer upstream binaries just because show upstream reports one. The tested/pinned relay-engine policy is part of release safety.
Last modified on September 10, 2026