feat: client cmd now uses the autonomi binary
#32
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jacderida
force-pushed
the
feat-safe_to_autonomi
branch
4 times, most recently
from
ff5031c to
a5ad217
Compare
The `client` command will now retrieve and install the `autonomi` binary rather than `safe`. The installer scripts have also been updated to use the new settings locations. BREAKING CHANGE: the binaries and settings now use a path with `autonomi` rather than `safe`. The old settings file is now also incompatible because it is at a different location and the field names have changed, so they will serialize/deserialize to/from different values. Fetching a different binary itself is also a breaking change. The tests in the PR workflow are updated to work with the newer versions of the `safenode` and `safenode-manager` binaries, which have new output for `--version`. We need to use RC versions just now because those are the only ones that have been released with the new versioning information.
jacderida
force-pushed
the
feat-safe_to_autonomi
branch
from
a5ad217 to
2305248
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
clientcommand will now retrieve and install theautonomibinary rather thansafe.The installer scripts have also been updated to use the new settings locations.
BREAKING CHANGE: the binaries and settings now use a path with
autonomirather thansafe. Theold settings file is now also incompatible because it is at a different location and the field names
have changed, so they will serialize/deserialize to/from different values. Fetching a different
binary itself is also a breaking change.
The tests in the PR workflow are updated to work with the newer versions of the
safenodeandsafenode-managerbinaries, which have new output for--version. We need to use RC versions justnow because those are the only ones that have been released with the new versioning information.