adiri upgrade -> v0.12.0-adiri - #5
Merged
Merged
Conversation
adiri moved to v0.12.0-adiri, so every default here follows: DEFAULT_DOCKER_IMAGE (the registry-unreachable fallback) in both lib/common.sh and ui/server.py, the setup wizard's docker-image placeholder, and MIN_SOURCE_VERSION_TESTNET 0.9.1 -> 0.12.0. The upgrade is wire-protocol-breaking: every libp2p protocol string is now namespaced by chain id, including the gossipsub protocol id itself, so a node left on v0.11 is not behind — it is partitioned, with no peers. The changelog entry says so plainly, along with the two things operators will ask about: no resync is needed (v0.12 reads existing v0 consensus packs), and a downgrade stops being clean once a v0.12 pack is written at the next epoch boundary. update-scripts.sh 1.1.62 -> 1.1.63 is what actually delivers all of the above to operators; lib/common.sh 1.3.5 -> 1.3.6 and ui 1.8.3 -> 1.8.4 ride along. Sidecars regenerated with tools/gen-checksums.sh — a stale one is fail-closed, and because lib/common.sh is force-added to every update set, a stale sidecar there would break updates fleet-wide. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
grantkee
changed the title
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
adiri moved to v0.12.0-adiri, so every default here follows: DEFAULT_DOCKER_IMAGE (the registry-unreachable fallback) in both lib/common.sh and ui/server.py, the setup wizard's docker-image placeholder, and MIN_SOURCE_VERSION_TESTNET 0.9.1 -> 0.12.0.
The upgrade is wire-protocol-breaking: every libp2p protocol string is now namespaced by chain id, including the gossipsub protocol id itself, so a node left on v0.11 is not behind — it is partitioned, with no peers. The changelog entry says so plainly, along with the two things operators will ask about: no resync is needed (v0.12 reads existing v0 consensus packs), and a downgrade stops being clean once a v0.12 pack is written at the next epoch boundary.
update-scripts.sh 1.1.62 -> 1.1.63 is what actually delivers all of the above to operators; lib/common.sh 1.3.5 -> 1.3.6 and ui 1.8.3 -> 1.8.4 ride along. Sidecars regenerated with tools/gen-checksums.sh — a stale one is fail-closed, and because lib/common.sh is force-added to every update set, a stale sidecar there would break updates fleet-wide.