Skip to content

chore(deps): update dependency canton-network/splice to v0.8.0 - #45

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/canton-network-splice-0.x
Open

chore(deps): update dependency canton-network/splice to v0.8.0#45
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/canton-network-splice-0.x

Conversation

@renovate

@renovate renovate Bot commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
canton-network/splice minor 0.7.50.8.0

How to check this and merge it

CI ran validate on this branch, so a service, profile or nginx route target that 0.8.0 moved is already red above. That check only reads files, which is why the steps below start the stack for real.

1. Get the branch

git fetch origin renovate/canton-network-splice-0.x
git switch renovate/canton-network-splice-0.x
npm ci

2. Clear what is running

Splice gives every container a fixed name (postgres, canton, nginx, and so on), so those names are global to Docker. Anything left from an earlier run blocks the start with Conflict. The container name "/postgres" is already in use. The second command removes those leftovers and nothing else.

npm run reset
docker ps -a --filter 'name=^/(postgres|canton|splice|nginx|console|swagger-ui|multi-sync-startup|multi-sync-ready|scan-web-ui|sv-web-ui|wallet-web-ui-sv|wallet-web-ui-app-user|ans-web-ui-app-user|wallet-web-ui-app-provider|ans-web-ui-app-provider)$' -q | xargs -r docker rm -f

3. Point your own config at 0.8.0

Renovate bumps the template. Your canton-barebones.config.json is a copy init made once and never overwrites, so without --force you would keep testing the old version. If you have local edits in that file or in splice-localnet-overrides.yaml, change splice.tag by hand instead: --force overwrites both.

npm run init -- --force

4. Start it

npm run validate   # must say 0.8.0 (compatible)
npm run start      # first run pulls the 0.8.0 images, give it a few minutes

5. Confirm it is serving

A running container is not the same as a live participant, so check the probe, not just the status.

npm run status
curl -sf http://localhost:2903/api/validator/readyz && echo "app-user ready"

6. Add the changeset

changeset-check stays red until this PR has one, and Renovate cannot add it itself.

npx changeset   # minor, summary: "Update Splice to 0.8.0"
git add .changeset && git commit -m "chore: add changeset for Splice 0.8.0" && git push

When you are done, npm run stop keeps the volumes and npm run reset wipes them.


Release Notes

canton-network/splice (canton-network/splice)

v0.8.0

Compare Source


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Backlog

Development

Successfully merging this pull request may close these issues.

1 participant