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.
Description
mithril-latest.yml
guild-deploy.sh
from the static version bump for mithril to obtaining the latest release.dockerfile_bin.yml
) when a push changesfiles/docker/node/release-versions/mithril-latest.txt
.Where should the reviewer start?
Testing via
./guild-deploy.sh -b mithril-latest-releases -s m
should update themithril-client --version
output to0.5.5+0780dfa
Motivation and context
Breaking changes between mithril release v2342.0 and v2347.0. Once the latest snaphot is signed by v2347.0 the v2342.0 client no longer works (for the latest snapshot).
Which issue it fixes?
Closes #1714
How has this been tested?
Running the current guild cardano-node:latest container, running
/opt/cardano/cnode/scripts/guild-deploy.sh -b mithril-latest-releases -s m
twice, once to update script the second to install Mithril's latest release. Thenconfirming the download starts without certificate errors.