deploy: node 1.0.1 #33

2026-09-15T09:21:02Z

grenade commented

2026-09-15 09:21:02 +00:00

Bump the pinned quantus-node from 0.11.1 to 1.0.1, the latest upstream release (2026-09-09).

Delta from 0.11.1 on the node side (git diff v0.11.1..v1.0.1): the mainnet chain spec is embedded so --chain mainnet works, command.rs changes four lines, and miner_server.rs and client/consensus/qpow are untouched. The v1.0.0-gm release notes state any node from v0.11.1 on is valid for mainnet. We keep running from the published asset/chainspec/mainnet.json with the same sha256, genesis assertion, bootnodes, chain id and miner credentials, so this is a binary swap only.

Why now: the fleet has been on 0.11.1 since the hand cutover, and this is the first push-triggered node deploy since. Merging exercises the whole CI path (fetch → deploy-node restart → validate → deploy-metrics) on mainnet. Expected mining interruption is the node restart plus miner reconnect, on the order of a minute.

Rollback: dispatch deploy with node_version: 0.11.1 and other inputs empty, per doc/mainnet-cutover.md.

🤖 Generated with Claude Code

https://claude.ai/code/session_01YJp25VomsWVZDPM9Fwmhnq

Bump the pinned quantus-node from 0.11.1 to 1.0.1, the latest upstream release (2026-09-09). **Delta from 0.11.1 on the node side** (`git diff v0.11.1..v1.0.1`): the mainnet chain spec is embedded so `--chain mainnet` works, `command.rs` changes four lines, and `miner_server.rs` and `client/consensus/qpow` are untouched. The v1.0.0-gm release notes state any node from v0.11.1 on is valid for mainnet. We keep running from the published `asset/chainspec/mainnet.json` with the same sha256, genesis assertion, bootnodes, chain id and miner credentials, so this is a binary swap only. **Why now:** the fleet has been on 0.11.1 since the hand cutover, and this is the first push-triggered node deploy since. Merging exercises the whole CI path (fetch → deploy-node restart → validate → deploy-metrics) on mainnet. Expected mining interruption is the node restart plus miner reconnect, on the order of a minute. **Rollback:** dispatch `deploy` with `node_version: 0.11.1` and other inputs empty, per `doc/mainnet-cutover.md`. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01YJp25VomsWVZDPM9Fwmhnq

grenade added 1 commit 2026-09-15 09:21:03 +00:00

deploy: node 1.0.1 5d179d9984

Upstream released v1.0.0-gm and v1.0.1 on mainnet day; the fleet has run
0.11.1 from the published mainnet.json since the hand cutover. The node-side
delta from 0.11.1 is small: the mainnet spec is embedded (`--chain mainnet`),
command.rs adjusts four lines, and the miner server and consensus client are
untouched. The release notes state any node from v0.11.1 on is valid, so this
is a binary swap on the same chain id, spec file and credentials.

This is also the first push-triggered node deploy since the cutover, which
is the point: prove the CI path upgrades bob without hand intervention.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01YJp25VomsWVZDPM9Fwmhnq

grenade merged commit 73aaf4119d into main

2026-09-15 09:21:20 +00:00

grenade referenced this issue from a commit

2026-09-15 09:21:21 +00:00

Merge pull request 'deploy: node 1.0.1' (#33) from node/v1.0.1 into main

grenade deleted branch node/v1.0.1

2026-09-15 09:21:22 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: lair/quantus#33