Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: client cmd now uses the autonomi binary #32

Merged
merged 1 commit into from
Oct 20, 2024

Conversation

jacderida
Copy link
Contributor

@jacderida jacderida commented Oct 20, 2024

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 jacderida force-pushed the feat-safe_to_autonomi branch 4 times, most recently from ff5031c to a5ad217 Compare October 20, 2024 17:11
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 jacderida force-pushed the feat-safe_to_autonomi branch from a5ad217 to 2305248 Compare October 20, 2024 17:20
@jacderida jacderida merged commit b3e8a86 into maidsafe:main Oct 20, 2024
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant