Skip to content

docs: add 2.1.0-beta.1 release notes - #2063

Open
ozgb wants to merge 1 commit into
mainfrom
ozgb-release-notes-2.1.0-beta.1
Open

docs: add 2.1.0-beta.1 release notes#2063
ozgb wants to merge 1 commit into
mainfrom
ozgb-release-notes-2.1.0-beta.1

Conversation

@ozgb

@ozgb ozgb commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

Overview

Adds the formatted release notes for node-2.1.0-beta.1 plus the two supporting docs they reference, following the layout already established by docs/release-notes/2.0.0-alpha.1/.

The notes are also the body of the GitHub release, so the docs need to live on main for the cross-doc links in that body to resolve — hence absolute blob/main/... URLs rather than relative paths.

File What it is
release-notes-2.1.0-beta.1.md v5-structured release notes
runtime-diff.md subwasm metadata diff, 1.0.3 → 2.1.0-beta.1
migration-hardfork-1.0.x.md operator runbook for the ledger 8 → 9 hard fork from a 1.0.3 chain

Two things worth a reviewer's eye:

  • Baseline. 2.0.0 never shipped a final release, so the change entries are the delta against the 2.0.0 pre-release line and against 1.0.3 — the supported fork-from baseline. Anything already carried by the 1.0.x maintenance line (the runtime-gated tblock correction feat(runtime): gate the tblock correction on a runtime upgrade #2002, the system_version bump to 3 chore: update system_version to 3 #1900) is deliberately not restated, and fix(ledger): serve ledger state reads at the ledger-hardfork set_code block #1985 is filed under Other Changes because on the 1.0.3 baseline the applying block is not a skew block.
  • How the runtime diff was produced. 1.0.3 is still pending, so there is no 1.0.3 WASM to feed subwasm, and this pre-release publishes no WASM asset either (Update srtool to Rust 1.95.0 #2061). git diff node-1.0.1 origin/release/node-1.0.3 -- runtime/ pallets/ changes only spec_version and system_version inside runtime/, so 1.0.3's pallet metadata surface is 1.0.1's; the pallet diff is taken between the published 1.0.1 and 2.1.0-beta.1 blobs and the version fields are read from the 1.0.3 branch source. The doc states this method inline, with the command to re-verify.

🗹 TODO before merging

  • Ready

📌 Submission Checklist

  • All commits are signed off (git commit -s) for the DCO
  • Changes are backward-compatible (or flagged if breaking)
  • Pull request description explains why the change is needed
  • Self-reviewed the diff
  • I have included a change file, or skipped for this reason: docs-only, no product surface affected
  • If the changes introduce a new feature, I have bumped the node minor version
  • Update documentation (if relevant)
  • Updated AGENTS.md if build commands, architecture, or workflows changed
  • No new todos introduced

🧪 Testing Evidence

Docs only — no code paths touched.

  • npx markdownlint-cli docs/release-notes/2.1.0-beta.1/*.md — clean (same disable list as the 2.0.0-alpha.1 notes).
  • Every intra-doc anchor and cross-doc link checked programmatically; all resolve.
  • Runtime diff regenerated with subwasm v0.21.3 against the runtime blobs extracted from the published midnightntwrk/midnight-node:1.0.1 and :2.1.0-beta.1 images.

Please describe any additional testing aside from CI:

  • Additional tests are provided (if possible)

🔱 Fork Strategy

  • Node Runtime Update
  • Node Client Update
  • Other:
  • N/A

Links

🤖 Generated with Claude Code

Formatted release notes for node-2.1.0-beta.1, plus the two supporting docs
they reference. Mirrors the layout of docs/release-notes/2.0.0-alpha.1/.

- release-notes-2.1.0-beta.1.md — v5-structured notes. The change entries are
  the delta against the 2.0.0 pre-release line and against 1.0.3, so anything
  shared with the 1.0.x maintenance line (the runtime-gated tblock correction,
  the system_version bump to 3) is not restated.
- runtime-diff.md — subwasm metadata diff 1.0.3 -> 2.1.0-beta.1. 1.0.3 is
  pending, so the pallet-surface diff is taken between the published 1.0.1 and
  2.1.0-beta.1 blobs; relative to 1.0.1 the 1.0.3 branch changes only
  spec_version and system_version inside runtime/, so the surface is identical.
- migration-hardfork-1.0.x.md — operator runbook for the ledger 8 -> 9 hard
  fork from a 1.0.3 chain.

Cross-doc links are absolute blob/main URLs so they also resolve from the
GitHub release page, which carries a copy of the notes as its body.

Assisted-by: Claude:claude-opus-5
Signed-off-by: Oscar Bailey <79094698+ozgb@users.noreply.github.com>
@ozgb
ozgb requested a review from a team as a code owner August 21, 2026 13:21
@ozgb ozgb added skip-changes-check-all skip-changes-check-issue bot:ai-assisted Authored or substantially edited by an AI agent labels Aug 21, 2026
--wasm-file midnight_node_runtime.compact.compressed.wasm \
-c <collective-signer-1> -c <collective-signer-2> \
-t <technical-signer-1> -t <technical-signer-2> \
--rpc-url ws://<node>:9944 \
--fetch-cache inmemory \
register-dust-address \
--wallet-seed <seed> \
-s ws://<node>:9944 -d ws://<node>:9944
--fetch-cache inmemory \
register-dust-address \
--wallet-seed <seed> \
-s ws://<node>:9944 -d ws://<node>:9944
--fetch-cache inmemory \
register-dust-address \
--wallet-seed <seed> \
-s ws://<node>:9944 -d ws://<node>:9944
--fetch-cache inmemory \
register-dust-address \
--wallet-seed <seed> \
-s ws://<node>:9944 -d ws://<node>:9944

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5b5cb9eb50

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".


```shell
cid=$(docker create midnightntwrk/midnight-node:2.1.0-beta.1)
docker cp "$cid:/artifacts-amd64/midnight_node_runtime.compact.compressed.wasm" .

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Select the runtime artifact directory by architecture

On an ARM host, this multi-architecture tag resolves to the arm64 image, which Earthfile builds with only /artifacts-arm64; the hardcoded /artifacts-amd64 path therefore makes the documented extraction step fail before the runtime upgrade. The checked .github/workflows/fork-network.yml handles this by probing both amd64 and arm64, and the runbook should do the same or derive the image architecture.

Useful? React with 👍 / 👎.

## Dependencies

- **midnight-ledger 9.1.0.0-rc.4** — pinned as a single workspace tag; the node binary provides it via host calls. Ledger 7 is fully removed, so this node cannot decode or replay chain history predating the ledger 7 → 8 hardfork.
- **The chain must already be running the 1.0.3 runtime** (pending release) — that is the fork-from baseline this release is built and tested against. Forking from 1.0.2 or earlier is not the documented path; see [Other Changes](#other-changes).

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Don't claim the 1.0.3 fork path is tested

The checked hard-fork pipeline does not test this baseline: util/toolkit/test-images.docker-compose.yml defaults FORK_FROM_NODE_IMAGE to midnightntwrk/midnight-node:1.0.1, and the accompanying migration guide explicitly says CI exercises the system_version: 1 skew-block path rather than the system_version: 3 path that arises from 1.0.3. Calling 1.0.3 “built and tested against” gives operators false assurance about the supported production fork path; either test with a 1.0.3 image/runtime or state that this exact path remains untested.

Useful? React with 👍 / 👎.

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

Labels

bot:ai-assisted Authored or substantially edited by an AI agent skip-changes-check-all skip-changes-check-issue

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants