Bump tacchaind v1.6.2-beta.2-manual→v1.6.4 (tac/tacchaind.Dockerfile) #99

Merged
sebastian merged 1 commits from vupd/5488-tacchaind-v1.6.4 into main 2026-10-05 10:24:09 +00:00
Collaborator

tacchaind v1.6.2-beta.2-manual → v1.6.4 — asset bump

Bumps ARG VERSION in tac/tacchaind.Dockerfile (v1.6.2-beta.2-manual → v1.6.4). The image downloads the prebuilt tacchaind-linux-amd64 binary from GitHub releases (TacBuild/tacchain) with sha256 checksum verification — no final-image registry tag.

Companion source PR: StakeSquid/vibe-node#5493 (context.yml bump on the same branch name). Both must merge together.

Changelog: https://github.com/TacBuild/tacchain/releases/tag/v1.6.4

Why

  • v1.6.3 coordinated mainnet upgrade activated 2026-09-14 10:00 UTC; our node on the pre-upgrade pin halted at the upgrade height (UPGRADE "v1.6.3" NEEDED) and has been down since. v1.6.4 ships the v1.6.3 handler + a JSON-RPC read-path fix (pre-v1.6.0 Ethereum tx decoding).
  • Release notes: no breaking changes — no ConsensusVersion bump, no StoreUpgrades, no flag/env/CLI/API changes; rolling restart vs v1.6.3.

Rollout

Rides the gitlink pin set by vibe-node#5493 after merge; deploy-compose-repo regenerates from this repo's main HEAD. Target host: rpc-de-32 (only tac deployment — tac/tacchaind/tac-mainnet-tacchaind-pruned). Post-deploy: node runs the v1.6.3 handler from the halt height then catches up ~19 days; fallbacks if the pruned datadir can't resume: statesync (polkachu) or Ankr archive snapshot.

Tracking issue: StakeSquid/vibe-node#5488

🤖 Generated with Claude Code

## tacchaind v1.6.2-beta.2-manual → v1.6.4 — asset bump Bumps `ARG VERSION` in `tac/tacchaind.Dockerfile` (`v1.6.2-beta.2-manual` → `v1.6.4`). The image downloads the prebuilt `tacchaind-linux-amd64` binary from GitHub releases (TacBuild/tacchain) with sha256 checksum verification — no final-image registry tag. Companion source PR: StakeSquid/vibe-node#5493 (context.yml bump on the same branch name). **Both must merge together.** Changelog: https://github.com/TacBuild/tacchain/releases/tag/v1.6.4 ### Why - v1.6.3 coordinated mainnet upgrade activated 2026-09-14 10:00 UTC; our node on the pre-upgrade pin halted at the upgrade height (`UPGRADE "v1.6.3" NEEDED`) and has been down since. v1.6.4 ships the v1.6.3 handler + a JSON-RPC read-path fix (pre-v1.6.0 Ethereum tx decoding). - Release notes: **no breaking changes** — no ConsensusVersion bump, no StoreUpgrades, no flag/env/CLI/API changes; rolling restart vs v1.6.3. ### Rollout Rides the gitlink pin set by vibe-node#5493 after merge; `deploy-compose-repo` regenerates from this repo's `main` HEAD. Target host: `rpc-de-32` (only tac deployment — `tac/tacchaind/tac-mainnet-tacchaind-pruned`). Post-deploy: node runs the v1.6.3 handler from the halt height then catches up ~19 days; fallbacks if the pruned datadir can't resume: statesync (polkachu) or Ankr archive snapshot. Tracking issue: StakeSquid/vibe-node#5488 🤖 Generated with [Claude Code](https://claude.com/claude-code)
claude added 1 commit 2026-10-03 03:37:29 +00:00
Author
Collaborator

merge-bot (del-018): classified B (hand-maintained rpc file(s), single scope). Auto-merge after a 72h objection window - comment 'hold' to block.

merge-bot (del-018): classified B (hand-maintained rpc file(s), single scope). Auto-merge after a 72h objection window - comment 'hold' to block.
sebastian merged commit b2ef60bfde into main 2026-10-05 10:24:09 +00:00
sebastian deleted branch vupd/5488-tacchaind-v1.6.4 2026-10-05 10:24:10 +00:00
Sign in to join this conversation.
No Reviewers
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: StakeSquid/ethereum-rpc-docker#99