Skip to content

chore: upgrade external node to v34.0.1 - #45

Merged
ccummings merged 2 commits into
mainfrom
chore/upgrade-external-node-v34.0.0-alpha
Nov 9, 2026
Merged

ccummings merged 2 commits into
mainfrom
chore/upgrade-external-node-v34.0.0-alpha

Conversation

@ccummings

@ccummings ccummings commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

Upgrading the external node to Matter Labs v34.0.1.

  • Chart version 0.1.50 → 0.1.51, appVersion v33.1.0 → v34.0.1
  • Image pinned to matterlabs/external-node:v34.0.1@sha256:ba3d1030097478a2d218b81d33aa2791507bac887cd43b98dd52492c52e695b8 (multi-arch, linux/amd64 and linux/arm64)
  • Docker Compose defaults and the mainnet/testnet env files updated to match

No new database migrations compared to v33.1.0.

@cursor

cursor Bot commented Nov 9, 2026 •

Copy link
Copy Markdown

PR Summary

Medium Risk
Upgrades production sync/RPC node binaries; schema is unchanged but rollout timing and chart release (0.1.51) affect live infra.

Overview
Bumps the Abstract external node from v33.1.0 to stable v34.0.1 across Helm and local Docker, matching Matter Labs’ v34 rollout.

The abstract-node chart is released as 0.1.51 with appVersion v34.0.1; default image.tag and digest point at the multi-arch Docker Hub index sha256:ba3d1030…. Docker Compose defaults for generate-secrets and external-node use the same version and digest, and new mainnet/testnet .env files pin those values for each network (same approach as prior upgrade PRs). No chart logic or migrations change—this is a version pin refresh only.

Reviewed by Cursor Bugbot for commit f8be4c7. Bugbot is set up for automated code reviews on this repo. Configure here.

@ccummings ccummings changed the title chore: upgrade external node to v34.0.0-alpha chore: upgrade external node to v34.0.1 Nov 9, 2026
@ccummings
ccummings merged commit e9b97c4 into main Nov 9, 2026
2 checks passed
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