Skip to content

chore(release)!: prepare 2.0.0-dev.1 - #1602

Merged
lklimek merged 2 commits into
devfrom
chore/release-2.0.0-dev.1
Nov 9, 2026
Merged

lklimek merged 2 commits into
devfrom
chore/release-2.0.0-dev.1

Conversation

@Claudius-Maginificent

@Claudius-Maginificent Claudius-Maginificent commented Nov 9, 2026 •

Copy link
Copy Markdown
Collaborator

TL;DR: Prepares the first Tenderdash 2.0 development prerelease, v2.0.0-dev.1, so Dash Platform can test the changes collected on dev since v1.8.2.

User story

As a Dash Platform developer, I want a versioned Tenderdash 2.0 prerelease with release notes, to test the new consensus, P2P and storage behavior against Platform before a stable release.

Scenario

Base flow

Platform teams pick up Tenderdash through versioned releases and Docker images.

Actual behavior

The changes merged to dev since v1.8.2 are only available as unversioned branch builds, and no release notes describe their breaking changes.

Expected behavior

After merge and tagging, v2.0.0-dev.1 is published as a GitHub prerelease with a dashpay/tenderdash:2.0.0-dev.1 image. Stable Docker aliases (latest, 1, 1.8) stay unchanged.

Detailed discussion

What was done

  • version/version.go: TMVersionDefault 1.8.2 → 2.0.0-dev.1, ABCISemVer 1.4.0 → 1.5.0, P2PProtocol 10 → 11. BlockProtocol stays 14.
  • CHANGELOG.md: new 2.0.0-dev.1 section with "Breaking Changes" (versioned contracts), "Migration Notes" (Go API, configuration, CLI) and protocol versions.

Release context:

Item Value
Candidate (frozen) origin/dev @ 0e08aa05c256e8bbe6702e01f6af8b77050bdce8
Compatibility baseline v1.8.2 @ dd596db0ddbde7e9a23754ddd6dbf6cc482fd9c1 (latest stable, reachable from the candidate, current master)
Range 64 commits, 574 files; none patch-equivalent to a stable release (scripts/release/plan.py --mode next)
Release type Prerelease from dev (first of the 2.0.0 series)

Version decision:

Dash Platform rollout:

  • Running 2.0.0-dev.1 nodes is safe with today's Platform chain parameters: consensus version 2 stays inactive until the application enables it.
  • Every node must run a version that supports consensus version 2 before Platform enables it (feat(consensus)!: hand a silent proposer's idle round to the next proposer #1572). Enabling it is out of scope here.
  • Operators must remove psql indexing, check P2P settings and set a supervisor grace period longer than --shutdown-timeout (30s).
  • Docker: prerelease tags publish only 2.0.0-dev.1 and never move stable aliases (scripts/tests/test_docker_metadata.py).

After merge: tag v2.0.0-dev.1 at the reviewed merge SHA, create a draft GitHub prerelease, attach signed Linux amd64/arm64 binaries (scripts/release/build-artifacts.sh), then publish it, which triggers docker.yml.

Testing

On the candidate plus this branch (the CHANGELOG-only follow-up commit needs no extra checks):

  • python3 -B -m unittest discover -s scripts/release -p test_release.py: 12 tests OK
  • python3 -B -m unittest discover -s scripts/tests -p test_docker_metadata.py: 16 tests OK
  • sh scripts/test-local-gates.sh: passed. shellcheck scripts/release/build-artifacts.sh: clean
  • gofmt -l version/ and go vet ./version/: clean. go build ./...: OK (CGO + BLS)
  • go test -count=1 -tags=deadlock ./version/... ./types/... ./abci/... ./internal/proxy/... ./node/...: all pass
  • The built binary reports 2.0.0-dev.1

Not verified here (CI covers the full suite):

  • Full race/e2e suites
  • Platform/Drive integration
  • A mixed-version network upgrade from 1.8.2
  • Activation of consensus version 2 on a Platform network

Breaking changes

This PR only changes release metadata. The prerelease it versions contains these breaking changes (CHANGELOG.md "Breaking Changes"):

Operator and integrator actions are listed under "Migration Notes".

Prior work

Attribution

Prepared with Claude Code (Claude Opus 5.5) using the tenderdash-release skill.

🤖 Generated with Claude Code

https://claude.ai/code/session_01WunYYgcoPDNh3uebhUCwig

🤖 Co-authored by Claudius the Magnificent AI Agent

PR Hygiene · cb19e3d

  • Bots — thepastaclaw ✓
  • Self-review — not asked of a bot author
  • Build green
  • Approvals
    • files with no dedicated owner (CHANGELOG.md, version/version.go) — approved by lklimek

When every merge requirement is met, the PR Hygiene check passes. Reviewer limits do not block merging; other required GitHub checks and protections still apply.

Bump TMVersionDefault to 2.0.0-dev.1, ABCISemVer to 1.5.0 and
P2PProtocol to 11; BlockProtocol stays 14. Add the 2.0.0-dev.1
changelog section reviewed against v1.8.2..0e08aa0.

<sub>🤖 Co-authored by [Claudius the Magnificent](https://github.com/lklimek/claudius) AI Agent</sub>

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WunYYgcoPDNh3uebhUCwig
@coderabbitai

coderabbitai Bot commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@thepastaclaw

thepastaclaw commented Nov 9, 2026 •

Copy link
Copy Markdown

✅ Final review complete — no blockers (commit cb19e3d) · triage: low

@lklimek

lklimek commented Nov 9, 2026

Copy link
Copy Markdown
Collaborator

/skip-bots

List consensus and RPC incompatibilities under Breaking Changes and move
Go API, configuration and CLI changes to Migration Notes, per the
versioning policy proposed in #1603. Add the broadcast_evidence change
from #1547.

<sub>🤖 Co-authored by [Claudius the Magnificent](https://github.com/lklimek/claudius) AI Agent</sub>

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WunYYgcoPDNh3uebhUCwig
@Claudius-Maginificent
Claudius-Maginificent marked this pull request as ready for review November 9, 2026 16:27

@thepastaclaw thepastaclaw 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.

Final validation — Phase 1 + Phase 2

Verified the release-preparation diff at cb19e3d and confirmed three non-blocking release-documentation inconsistencies. No blocking defect was established in the version updates or their compatibility consumers. This was a static review; current CI shows all build, test, and lint checks passing, with only the automated review pending.

🟡 3 suggestion(s)

2 finding(s) not shown inline (the lines are not part of this PR's diff)

🟡 Suggestion: Align the published RPC reference with the release version
rpc/openapi/openapi.yaml:52-55

The RPC reference still identifies itself as v1.8-dev and links the license to that branch, while this PR prepares v2.0.0-dev.1 with explicitly changed RPC contracts. scripts/prepare-docs.py copies rpc/openapi verbatim into the published documentation; DOCS_SOURCE_REF rewrites Markdown source links, not this YAML metadata. This is a missed sibling version marker in release preparation: update it so the reference accompanying the release does not identify the previous development line.

  version: "v2.0.0-dev.1"
  license:
    name: Apache 2.0
    url: https://github.com/dashpay/tenderdash/blob/v2.0.0-dev.1/LICENSE

source: glm-5.3-flash (phase1-reviewer: general)

🟡 Suggestion: Associate the upgrade instructions with this prerelease
UPGRADING.md:5

The Unreleased section contains the P2P startup validation, service-lifecycle, commit vote-extension verification, and cached transaction-rejection changes included in this release. Leaving these instructions unversioned while assigning the release makes it unclear which upgrade first requires those actions, particularly once subsequent development adds more notes. File the existing section under v2.0.0-dev.1, consistent with the version-specific purpose of this guide and the earlier v1.7.0 organization; future changes can start a new Unreleased section.

## v2.0.0-dev.1

source: glm-5.3-flash (phase1-reviewer: general)

Review provenance

Source: reviewer 1: glm-5.3-flash (agent: phase1-reviewer, role: general); reviewer 2: gpt-6.1-sol (agent: phase2-reviewer, role: general); final verifier: gpt-6.1-sol (agent: sol-verifier, role: final-verifier)

  • Triage: low by gpt-6.1-sol (effort low) — The diff is limited to release notes and three version constants, making it small and well-contained without changing consensus rules or protocol implementations.
  • Phase 1 reviewers: glm-5.3-flash — general (completed, effort high); agent phase1-reviewer
  • Phase 1 model: glm-5.3-flash — zai quota: 5h 97% left, weekly 99% left; passed over gemini-3.8-flash-high (antigravity quota lookup failed)
  • Fresh verifier: gpt-6.1-sol — final-verifier; agent sol-verifier
  • Phase 2 reviewers: gpt-6.1-sol — general (completed, effort medium); agent phase2-reviewer
🤖 Prompt for all review comments with AI agents
These findings are from an automated code review. Verify each finding against the current code and only fix it if needed.

In `CHANGELOG.md`:
- [SUGGESTION] CHANGELOG.md:77: Describe the net linter change rather than the superseded pin
  The release notes advertise a golangci-lint v2.14.0 pin, but Makefile, go.mod, and the lint workflow all specify v2.15.0 at both the v1.8.2 baseline and this release head. Although #1524 temporarily introduced that pin, subsequent changes superseded it before this release. The actual net change is the migration from gomodguard to gomodguard_v2; retain that migration without naming a linter version the release does not ship.

In `rpc/openapi/openapi.yaml`:
- [SUGGESTION] rpc/openapi/openapi.yaml:52-55: Align the published RPC reference with the release version
  The RPC reference still identifies itself as v1.8-dev and links the license to that branch, while this PR prepares v2.0.0-dev.1 with explicitly changed RPC contracts. scripts/prepare-docs.py copies rpc/openapi verbatim into the published documentation; DOCS_SOURCE_REF rewrites Markdown source links, not this YAML metadata. This is a missed sibling version marker in release preparation: update it so the reference accompanying the release does not identify the previous development line.

In `UPGRADING.md`:
- [SUGGESTION] UPGRADING.md:5: Associate the upgrade instructions with this prerelease
  The Unreleased section contains the P2P startup validation, service-lifecycle, commit vote-extension verification, and cached transaction-rejection changes included in this release. Leaving these instructions unversioned while assigning the release makes it unclear which upgrade first requires those actions, particularly once subsequent development adds more notes. File the existing section under v2.0.0-dev.1, consistent with the version-specific purpose of this guide and the earlier v1.7.0 organization; future changes can start a new Unreleased section.

Comment thread CHANGELOG.md
- Pin Docker workflow actions to commit SHAs and restrict token permissions (#1589)
- Replace Janitor with native PR concurrency (#1592)
- Migrate proto lint to buf-action (#1561)
- Pin golangci-lint to v2.14.0 and migrate to gomodguard_v2 (#1524)

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🟡 Suggestion: Describe the net linter change rather than the superseded pin

The release notes advertise a golangci-lint v2.14.0 pin, but Makefile, go.mod, and the lint workflow all specify v2.15.0 at both the v1.8.2 baseline and this release head. Although #1524 temporarily introduced that pin, subsequent changes superseded it before this release. The actual net change is the migration from gomodguard to gomodguard_v2; retain that migration without naming a linter version the release does not ship.

Suggested change
- Pin golangci-lint to v2.14.0 and migrate to gomodguard_v2 (#1524)
- Migrate gomodguard to gomodguard_v2 (#1524)

source: glm-5.3-flash (phase1-reviewer: general)

@github-actions

github-actions Bot commented Nov 9, 2026 •

Copy link
Copy Markdown

Ready for review — files with no dedicated owner: lklimek or shumkov.
Full checklist in the description.

@github-actions github-actions Bot added the ready-for-human PR Hygiene: bots done, author self-reviewed, awaiting human review label Nov 9, 2026
@github-actions
github-actions Bot requested review from lklimek and shumkov November 9, 2026 19:10
@lklimek
lklimek enabled auto-merge (squash) November 9, 2026 20:25
@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown

Policy satisfied — this can merge.
Full checklist in the description.

@github-actions github-actions Bot removed the ready-for-human PR Hygiene: bots done, author self-reviewed, awaiting human review label Nov 9, 2026
@lklimek
lklimek merged commit 683b8ac into dev Nov 9, 2026
26 checks passed
@lklimek
lklimek deleted the chore/release-2.0.0-dev.1 branch November 9, 2026 20:26
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.

3 participants