Due to protocol versioning, it is highly recommended to keep clients up to date. This release simplifies the process, bringing inline client upgrade functionality, including an upgrade supervisor, migration and rollback support. The required version is specified by the contract operator-owned directory.
This sequence diagram shows the high-level flow of a client
upgrade and
the behind the scenes interaction it has with other Wireleap components.
The upgrade process is interactive so you will have the possibility to accept or decline based on the changelog for the new release version.
wireleap upgrade
If the upgrade was successful, the old binary is not deleted but kept as wireleap.prev for rollback purposes, in case issues manifest post-upgrade.
wireleap rollback
If the upgrade was not successful, it is possible to skip the faulty version explicitly.
# skip upgrades to version 1.2.3
echo "1.2.3" > $HOME/wireleap/.skip-upgrade-version
wireleap
Manual client upgrade support:
upgrade
and rollback
commandsinit --force-unpack-only
to only overwrite embedded filesexec
scripts are now located in scripts/default/
UI fixes and improvements:
https://
URLexec
scripts are now located in scripts/default/
exec
scripts in scripts/
take precedencewireleap tun
Default circuit.hops
changed to 1
Fixed issue where some errors during initial splice weren’t reported
wireleap-relay
wireleap-contract
Configuration changes:
icon
, banner
.operator_url
.Endpoint changes:
/info/X
field getter support removed./info/
changed to /info
.wireleap-dir
update_channels.client
for specifying the required version./info
endpoint versioning to allow for client upgrades.Version
0.3.1
Next Article
Side by side traffic comparisonPrevious Article
Rebranded software suite to WireleapNo results found
client
=dataflow
'circuit
!docs
^installation
paper$
White space acts as an AND operator, while a single pipe
(|
) character acts as an OR operator. To escape
white space, use double quotes such as ="wireleap
client"
for an exact match.