Skip to content

feat(splice): catalogue Splice 0.6.13–0.8.1, default 0.8.1 - #336

Open
srikanth-bitdynamics wants to merge 1 commit into
mainfrom
feat/splice-0.8-versions
Open

feat(splice): catalogue Splice 0.6.13–0.8.1, default 0.8.1#336
srikanth-bitdynamics wants to merge 1 commit into
mainfrom
feat/splice-0.8-versions

Conversation

@srikanth-bitdynamics

Copy link
Copy Markdown
Collaborator

DevNet is moving to 0.8.0, but the catalogue stopped at 0.6.12 — so localnet up --version 0.8.x had neither a catalogue entry nor an adapter. This bumps supported versions through 0.8.1 and adds them to the version matrix.

What's in it

  • Catalogue (internal/splice/versions.json): every stable upstream tag from 0.6.13 through 0.8.10.6.13, 0.6.14, 0.7.00.7.5, 0.8.0, 0.8.1. Each carries the real pinned commit + ContentSHA computed by scripts/add-splice-version.sh (downloads the upstream cluster/compose/localnet/ tree and hashes it). New 0.7/0.8 majors get the 8/12 GB memory floor.
  • latest_alias0.8.1: --version latest and the Web UI default now track DevNet.
  • Adapters: new internal/splice/v07 and v08. I diffed the upstream cluster/compose/localnet/ tree at 0.6.12 vs 0.8.0 — identical file set, identical env/ set, same profiles (sv/app-provider/app-user/swagger-ui), and the same env-var contract the adapter wires (IMAGE_TAG, IMAGE_REPO, PARTY_HINT, ALPHA_PROTOCOL_VERSION_ENV, …) — so v07/v08 embed the v06 adapter and only relabel the major. Registered both in internal/localnet/adapters.go.
  • Docs: fixed the stale memory-floor enumeration in docs/limitations.md (0.6.9/latest → covers the 0.6/0.7/0.8 lines). The version matrix itself is rendered from the catalogue by dpm localnet versions.
  • Tests: SupportsTokenStandardV2 now covers 0.8.x; the adapter core-services agreement test checks 0.8.0 resolves through the new v08 adapter.

CLI ↔ Web UI parity

The catalogue is the single shared source — the CLI (localnet versions, --version) and the Web UI version picker both read it, so both surfaces gain the new versions together. internal/ui/handlers tests pass.

Verification

gofmt clean, go vet clean, go build ./... OK, and go test passes for internal/splice/..., internal/localnet/..., internal/cli/localnet/..., internal/ui/handlers/.... localnet versions --offline lists 0.6.13–0.8.1 as supported.

⚠️ Not yet boot-validated

This is catalogue + adapter wiring; I have not run localnet up --version 0.8.1 against Docker to confirm the stack actually comes up (image availability at the default repo/tag, any new required env, real memory footprint). Since this makes 0.8.1 the default --version, a real boot test on 0.8.x should gate the release that ships it.

🤖 Generated with Claude Code

DevNet is moving to 0.8.0 and the catalogue stopped at 0.6.12, so
`localnet up --version 0.8.x` had no entry and no adapter. Add every
stable upstream tag from 0.6.13 through 0.8.1 (real pinned commit +
ContentSHA via scripts/add-splice-version.sh) and register the 0.7 and
0.8 majors.

The cluster/compose/localnet/ interface is unchanged from 0.6.x upstream
— verified identical file/env set, same profiles, and the same env-var
contract the adapter wires — so the v07/v08 adapters embed the v06
adapter and only relabel the major. Set latest_alias to 0.8.1 so
`--version latest` (and the Web UI default) track DevNet, and give the
new 0.7/0.8 majors the empirically-derived 8/12 GB memory floor.

Catalogue and adapter wiring only; not yet boot-validated on 0.8.x. A
real `localnet up --version 0.8.1` should gate the release that ships
this as the default.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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