As mentioned in the Monolithic wireleap repository split, released under MIT post, consumer-provider semantic versioning was in the works. Initial support has now been implemented and released in the latest component versions, along with other improvements.
Please note, this is a backwards incompatible release.
Previously, all components shared the same semantic software release and protocol version. This worked quite well and was convenient, but required a full software suite version bump for each change.
$ wireleap version
0.3.2, protocol version 0.3.2
With the split, each component received its own software version depicted by the git tag, and depended on a specific version of common, but still used a “common protocol version”.
With this release, each component now inherits the interface versions as defined in common for API consumer-provider intercomponent communication, allowing for versions to be bumped individually as needed, while adhering to the semantic versioning specification.
$ wireleap version -v
0.4.0
client-dir interface version 0.1.0
client-relay interface version 0.1.0
client-contract interface version 0.1.0
$ wireleap-relay version -v
0.4.0
client-relay interface version 0.1.0
relay-dir interface version 0.1.0
relay-relay interface version 0.1.0
relay-contract interface version 0.1.0
Note: Releases are based on semantic versioning, and use the format MAJOR.MINOR.PATCH. While the MAJOR version is 0, MINOR version bumps are considered MAJOR bumps per the semver spec. https://wireleap.com/docs/client/#versioning
common
api/client and api/provide to perform interface version
checks.-v) option added to version command to display interface
versions.wireleap
wireleap/common v0.2.1.bypass.json generation logic to cover edge cases.config circuit.whitelist now accepts space-separated list of
relays to use.firefox exec script.reload.clientdir v0.1.0clientcontract v0.1.0clientrelay v0.1.0wireleap-relay
wireleap/common v0.2.1.version command code.clientrelay v0.1.0relaycontract v0.1.0relaydir v0.1.0relayrelay v0.1.0wireleap-contract
wireleap/common v0.2.1.version command code.clientcontract v0.1.0relaycontract v0.1.0contractps v0.1.0wireleap-auth
wireleap/common v0.2.1.version command code.psauth v0.1.0contractps v0.1.0 (for unit testing only)relaycontract v0.1.0 (for unit testing only)wireleap-dir
wireleap/common v0.2.1.version command code.clientdir v0.1.0relaydir v0.1.0ps-dummy
wireleap/common v0.2.1.version command code.psauth v0.1.0contractps v0.1.0ps-stripe
wireleap/common v0.2.1.version command code.psauth v0.1.0contractps v0.1.0Version
0.4.0
Next Article
Utilizing h/2 headers - cleaner, simpler, fasterPrevious Article
Client bash completionNo results found
client=dataflow'circuit!docs^installationpaper$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.