docs(operators): 1.1.8 → 1.2.0 upgrade notes#1815
Open
omersadika wants to merge 2 commits into
Open
Conversation
Operator-facing rollout notes for everything 1.2.0 changes at the operational surface: the ika-node binary/image split (and the boot-time role validation that rejects a validator YAML still carrying notifier_client_key_pair), the old-style config guarantees and the two fail-closed edges, the fleet-wide ika_ metric-prefix rename (dashboards re-key or go dark), the jemalloc allocator switch, exec-bit caveat for raw GCP binary downloads, the unchanged 16-core validator minimum, and mixed-version-window guidance. Written as item 6 of the 1.2.0 pre-tag checklist from the release review; intended to also be pasted/linked into the GitHub release notes at tag time. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…nfig-key casing; upgrade is a coordinated swap Review corrections: 1. The v4 paragraph claimed "protocol version 4 activates later by validator vote" — wrong: the binary advertises v3..=v4 (SupportedProtocolVersions::SYSTEM_DEFAULT), capabilities are tallied at every epoch close, and v4 activates AUTOMATICALLY roughly one epoch after quorum+buffer stake runs 1.2.0. Completing the rollout is itself what schedules the activation; operators must plan with that. 2. sui_data_source -> sui-data-source (serde kebab-case; operators paste keys literally). 3. Section 7 rewritten from "rolling window, keep it short" to the coordinated-atomic-swap guidance the cross-binary contract actually requires: 1.1.8 and 1.2.0 link different crypto libraries, mixed committees cannot exchange MPC messages, the mainnet rehearsal swaps all validators at once, and a never-completable in-flight session can hold up the epoch — so the fleet should restart near-simultaneously, away from an epoch boundary. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
What
Item 6 of the 1.2.0 pre-tag checklist: the operator-facing rollout notes the release review found missing. Adds
docs/content/docs/operators/upgrading-to-1-2-0.mdx(the Operators docs section was a "Coming Soon" stub; in-reponre/helm material no longer exists, anddashboards/is a placeholder — so this page is the single place operators can be pointed to).Covers, all verified against the code during the review:
ika-node→ika-validator/ika-fullnode/ika-notifier(+ registry paths and tag format), and the boot-time role validation that rejects a validator YAML still carryingnotifier_client_key_pair(ika-config/src/node.rs:84).sui-rpc-urlYAMLs keep JSON-RPC for every role (fix(ika-config): old-style config keeps legacy JSON-RPC for every role #1791); the two fail-closed edges (no-URL default removed;sui_data_sourcemigration requires a gRPC endpoint).ika_prefix fleet-wide, Mysticeti underika_consensus_*, ~85 dead metrics deleted; points at commit c34f9a3 as the authoritative old→new map.LD_PRELOADworkarounds).chmod +x(tarballs/brew/docker fixed by fix(release): restore the executable bit on published binaries + de-collide per-network release names #1811).Intended to be pasted/linked into the GitHub draft-release body at tag time.
🤖 Generated with Claude Code