feat(splice): catalogue Splice 0.6.9, 0.6.10, and 0.6.11 - #246
Merged
Conversation
Adds the three release lines the networks currently run — mainnet 0.6.9, testnet 0.6.10, devnet 0.6.11 — to the curated catalogue, so both `dpm localnet up --version <tag>` and the Web UI version picker offer them. Commits and content SHAs were resolved from canton-network/splice via scripts/add-splice-version.sh, not hand-written. 0.6.10 and 0.6.11 share a content SHA because their cluster/compose/localnet subtrees are byte- identical (confirmed against the git tree SHA); their full-archive sizes differ. All three inherit the 0.6 line's 8 GB / 12 GB memory floors. The default (`latest_alias`) is set to 0.6.9 — the mainnet release — so a bare `localnet up` gives the most conservative supported version. Also orders Supported() numerically instead of lexically: without it "0.6.10" sorted before "0.6.3", so the CLI's --version list disagreed with the semver-sorted Web UI picker. Adds compareTags/parseSemver with tests.
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.
What
Adds the three Splice release lines the networks currently run to the curated version catalogue:
latest)Both surfaces pick them up automatically from the shared catalogue —
dpm localnet up --version <tag>and the Web UI version picker.How the values were obtained
Commits and content SHAs were resolved from
canton-network/spliceviascripts/add-splice-version.sh(the maintainer flow), not hand-written:0.6.9→bc6a3587…0.6.10→63cfb340…0.6.11→fd93f86a…0.6.10and0.6.11share acontent_sha— theircluster/compose/localnet/subtrees are byte-identical (verified independently against the git tree SHA1f23b7f0…); only the rest of each release archive differs, hence differentsize. All three inherit the 0.6 line's 8 GB / 12 GB memory floors.Default version
latest_aliasis set to 0.6.9 (mainnet) — a barelocalnet upgives the most conservative supported version.--version 0.6.10/0.6.11opt into the newer lines.Bonus: numeric version ordering
Supported()sorted lexically, so0.6.10came before0.6.3— which broke CLI↔UI parity (the Web UI already sorts semver-aware). Fixed withcompareTags/parseSemver(numeric major.minor.patch, non-semver tags last), with unit tests. The CLI's--versionlist now reads0.5.18, 0.6.3, 0.6.4, 0.6.9, 0.6.10, 0.6.11, token-standard-v2.Verification
go build,go vet,gofmt, full Go suite green (incl. newcompareTags/ numeric-order tests).up --helplists the versions in numeric order;"latest" resolves to 0.6.9;--version 0.6.11accepted;localnet versionsmarks all three supported.docs/limitations.mdupdated to reflect the new 0.6 line + default.