StakeSquid/ethereum-rpc-docker
1
0
Fork 0
Code Issues Pull Requests 3 Packages Projects Releases Wiki Activity

Bump sonic v2.1.6 → v2.2.0 (Go base 1.24 → 1.26) #34

Merged
sebastian merged 1 commits from vupd/924-sonic-v2.2.0 into main 2026-07-06 09:08:46 +00:00
Conversation 0 Commits 1 Files Changed 1 +2 -2
claude commented 2026-07-06 02:31:55 +00:00
Collaborator
Copy Link

Bump sonic v2.1.6 → v2.2.0 — Dockerfile (Go 1.24 → 1.26)

Asset change: sonic/sonic.Dockerfile — Go base image bumped from golang:1.24 to golang:1.26 (both build and runtime stages). Required because sonic v2.2.0's go.mod specifies go 1.26.0; the old base would fail to build.

Release notes: https://github.com/0xsoniclabs/sonic/releases/tag/v2.2.0

Hardfork — Brio

v2.2.0 activates the Brio hard-fork (no on-chain activation date announced; fork support is compiled in). New capabilities under Brio: Transaction Bundles, EIP-7939 (CLZ), EIP-7951 (secp256r1), EIP-7883/7823/7825/7934; contract/init-code size limits raised (48 KiB / 96 KiB).

Breaking changes

  • Many debug_* namespace methods removed
  • trace_call output format changed — now includes stateDiff structure (consumers relying on old format must update)

What the developer did

  1. This PR — bumps golang:1.24 → golang:1.26 in both stages of sonic/sonic.Dockerfile; no genesis, entrypoint, or template changes needed.
  2. Companion vibe-node PR (vupd/924-sonic-v2.2.0) — bumps chains.sonic.clients.sonic.client_version v2.1.6 → v2.2.0 in context.yml.
  3. Brio fork activation is chain-protocol driven; existing genesis URLs unchanged.
  4. ./update.sh verify: clean (559 files, 0 errors).

Rollout plan

After both this PR and the companion vibe-node PR merge: deploy-compose-repo to one representative sonic host, verify sync-status shows v2.2.0 and no crashloop; then fleet roll.

Companion issue: StakeSquid/vibe-node#924

## Bump sonic v2.1.6 → v2.2.0 — Dockerfile (Go 1.24 → 1.26) **Asset change:** `sonic/sonic.Dockerfile` — Go base image bumped from `golang:1.24` to `golang:1.26` (both build and runtime stages). Required because sonic v2.2.0's `go.mod` specifies `go 1.26.0`; the old base would fail to build. **Release notes:** https://github.com/0xsoniclabs/sonic/releases/tag/v2.2.0 ### Hardfork — Brio v2.2.0 activates the **Brio hard-fork** (no on-chain activation date announced; fork support is compiled in). New capabilities under Brio: Transaction Bundles, EIP-7939 (CLZ), EIP-7951 (secp256r1), EIP-7883/7823/7825/7934; contract/init-code size limits raised (48 KiB / 96 KiB). ### Breaking changes - Many `debug_*` namespace methods **removed** - `trace_call` output format changed — now includes `stateDiff` structure (consumers relying on old format must update) ### What the developer did 1. **This PR** — bumps `golang:1.24` → `golang:1.26` in both stages of `sonic/sonic.Dockerfile`; no genesis, entrypoint, or template changes needed. 2. **Companion vibe-node PR** (`vupd/924-sonic-v2.2.0`) — bumps `chains.sonic.clients.sonic.client_version` v2.1.6 → v2.2.0 in `context.yml`. 3. Brio fork activation is chain-protocol driven; existing genesis URLs unchanged. 4. `./update.sh` verify: **clean** (559 files, 0 errors). ### Rollout plan After both this PR and the companion vibe-node PR merge: `deploy-compose-repo` to one representative sonic host, verify `sync-status` shows v2.2.0 and no crashloop; then fleet roll. _Companion issue: StakeSquid/vibe-node#924_
claude added 1 commit 2026-07-06 02:31:56 +00:00
sonic: bump Dockerfile Go base image 1.24 -> 1.26 for v2.2.0 1760023975 
v2.2.0 requires go 1.26.0 per upstream go.mod.
sebastian merged commit 1760023975 into main 2026-07-06 09:08:46 +00:00
sebastian deleted branch vupd/924-sonic-v2.2.0 2026-07-06 09:08:47 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claude cursor rob sebastian
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: StakeSquid/ethereum-rpc-docker#34
Delete Branch "vupd/924-sonic-v2.2.0"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?