Skip to content

chore: release v1.5.1#196

Merged
lklimek merged 1 commit into
developfrom
release/v1.5.1
Apr 24, 2026
Merged

chore: release v1.5.1#196
lklimek merged 1 commit into
developfrom
release/v1.5.1

Conversation

@lklimek

@lklimek lklimek commented Apr 24, 2026

Copy link
Copy Markdown
Collaborator

Issue being fixed or feature implemented

Cuts patch release v1.5.1 off develop. Collects nine dependency bumps and one build-script fix that have accumulated since v1.5.0 (2026-01-27), plus an MSRV update forced by the zip 8.5 build-dependency.

What was done?

How Has This Been Tested?

  • cargo check --workspace — clean at 1.5.1.
  • All CI checks on develop have been green since merging the nine PRs (see individual PRs for per-change verification).

Breaking Changes

Effective MSRV bump: tenderdash-proto-compiler now requires rustc ≥ 1.88 (via zip 8.5). Because proto-compiler is a [build-dependencies] of tenderdash-proto, every downstream consumer building tenderdash-proto needs rustc ≥ 1.88. Reflected in rust-version = "1.88" so cargo gives a clean error on older toolchains instead of a cryptic zip MSRV failure.

Per Rust API Guidelines this is a minor bump, but releasing as patch per maintainer preference; MSRV change is documented in the changelog.

Checklist

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have added or updated relevant unit/integration/functional/e2e tests (N/A — release metadata only)
  • I have made corresponding changes to the documentation (CHANGELOG.md created)

For repository code-owners and collaborators only

  • I have assigned this pull request to a milestone

Post-merge steps

After merging:

  1. Tag v1.5.1 on the resulting develop HEAD and push.
  2. Pushing the tag triggers .github/workflows/release.yml → runs ./release.sh → publishes to crates.io (needs CRATES_TOKEN).
  3. Open a companion PR in dashpay/platform to bump the tenderdash-abci / tenderdash-proto refs to v1.5.1 (45 Cargo.toml files touched by scripts/release.sh; not included here).

🤖 Co-authored by Claudius the Magnificent AI Agent

Summary by CodeRabbit

  • Chores

    • Version bumped to 1.5.1
    • Updated minimum Rust version requirement to 1.88
    • Bumped dependencies and Docker base images
    • Upgraded CI/build workflow action versions
  • Bug Fixes

    • Resolved test suite issues

- workspace version 1.5.0 -> 1.5.1
- rust-version 1.85 -> 1.88 (zip 8.5 build-dep requires rustc >= 1.88)
- add CHANGELOG.md (Keep a Changelog format) with [1.5.1] entry

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Apr 24, 2026

Copy link
Copy Markdown
Contributor
📝 Walkthrough

Walkthrough

Version bump from 1.5.0 to 1.5.1 with updated Rust MSRV from 1.85 to 1.88. CHANGELOG.md documents release notes including dependency updates, test fixes, and CI workflow action upgrades.

Changes

Cohort / File(s) Summary
Version and Configuration Update
Cargo.toml, CHANGELOG.md
Incremented workspace version to 1.5.1, raised Rust MSRV to 1.88, and documented release notes including dependency bumps (zip), test fixes in tenderdash-proto-compiler and tenderdash-abci, and CI action version upgrades.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A hop, a skip, one-eighty-eight we go,
Rust version climbs, our projects grow,
Point-five-one blooms in the changelog's glow,
Dependencies dance, workflows aglow,
Carrots and configs align just so! 🥕✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'chore: release v1.5.1' directly and clearly identifies the main purpose of the PR: cutting a patch release v1.5.1, which aligns with the primary changes (version bump in Cargo.toml and CHANGELOG.md entry).
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release/v1.5.1

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

Comment @coderabbitai help to get the list of available commands and usage tips.

@lklimek
lklimek marked this pull request as ready for review April 24, 2026 09:24

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@Cargo.toml`:
- Around line 5-8: The workspace.package table in Cargo.toml is missing the
edition field; update the workspace.package section to include edition = "2024"
alongside the existing rust-version = "1.88" and version = "1.5.1" so the
manifest explicitly sets the Rust edition, and apply the same edition = "2024"
addition to any crate-level Cargo.toml files as required by project guidelines.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 6e746cf1-5be1-4935-b45f-06fa4b437564

📥 Commits

Reviewing files that changed from the base of the PR and between fb27e3a and c1c70fe.

📒 Files selected for processing (2)
  • CHANGELOG.md
  • Cargo.toml

Comment thread Cargo.toml
Comment on lines 5 to +8
[workspace.package]

rust-version = "1.85"
version = "1.5.0"
rust-version = "1.88"
version = "1.5.1"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Add missing edition = "2024" to workspace.package.

The workspace.package section specifies rust-version but is missing the edition field. As per coding guidelines, Cargo.toml files must set Rust edition to 2024 and specify rust-version in workspace and crate Cargo manifests.

📝 Proposed fix to add edition field
 [workspace.package]
 
 rust-version = "1.88"
+edition = "2024"
 version = "1.5.1"

Based on learnings: Set Rust edition to 2024 and specify rust-version in workspace and crate Cargo manifests.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
[workspace.package]
rust-version = "1.85"
version = "1.5.0"
rust-version = "1.88"
version = "1.5.1"
[workspace.package]
rust-version = "1.88"
edition = "2024"
version = "1.5.1"
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@Cargo.toml` around lines 5 - 8, The workspace.package table in Cargo.toml is
missing the edition field; update the workspace.package section to include
edition = "2024" alongside the existing rust-version = "1.88" and version =
"1.5.1" so the manifest explicitly sets the Rust edition, and apply the same
edition = "2024" addition to any crate-level Cargo.toml files as required by
project guidelines.

@lklimek
lklimek merged commit fae4729 into develop Apr 24, 2026
12 checks passed
@lklimek
lklimek deleted the release/v1.5.1 branch April 24, 2026 09:43
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.

1 participant