build(dashmate): update Tenderdash image to v1.6.0

[Claudius-Maginificent]

Why this PR exists

• Problem: dashmate pinned an older Tenderdash image (1.6-dev.1). The Tenderdash 1.6.0 line is now final and published on Docker Hub.
• What breaks without it: nodes provisioned by dashmate keep running an outdated Tenderdash build, missing every 1.6.0 change.

What was done

• Bumped the default Tenderdash image in packages/dashmate/configs/defaults/getBaseConfigFactory.js to the final dashpay/tenderdash:1.6.0.
• Folded the image bump into the 4.0.0-rc.3 config migration in packages/dashmate/configs/getConfigFileMigrationsFactory.js so existing user configs upgrade on dashmate update. The image is pulled DRY from the base config, so the migration tracks whatever the base config pins.
  • Keyed at 4.0.0-rc.3 (the next unreleased version), not the already-released 4.0.0-rc.2: the migration runner skips fromVersion === toVersion, so a key equal to an operator's current version never fires. Backfill runs once the package bumps to rc.3.
  • The 4.0.0-rc.3 migration already carried the rate-limiter responseHeaders backfill from base; both backfills now share that single migration (a duplicate object key would silently overwrite).

Testing

• Confirmed dashpay/tenderdash:1.6.0 is published on Docker Hub (multi-arch amd64/arm64, pushed 2026-06-26).
• yarn workspace dashmate lint → 0 errors.
• node --check passes on both modified files.

Breaking Changes

• None.

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
• I have added "!" to the title and described breaking changes in the corresponding section if my code contains any
• I have made corresponding changes to the documentation if needed

For repository code-owners and collaborators only

• I have assigned this pull request to a milestone

_{🤖 Co-authored by Claudius the Magnificent AI Agent}

[coderabbitai]

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 3d54d94c-4dbe-4143-82ed-3b0ea75f0e07

📥 Commits

Reviewing files that changed from the base of the PR and between 1653b89 and 7a7b212.

📒 Files selected for processing (2)

• packages/dashmate/configs/defaults/getBaseConfigFactory.js
• packages/dashmate/configs/getConfigFileMigrationsFactory.js

 ______________________________________________
< Looking for trouble in all the right places. >
----------------------------------------------
\
\ \
\ /\
( )
.( o ).

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch build/dashmate-tenderdash-1.6.0-dev.2

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[thepastaclaw]

✅ Review complete (commit 7a7b212)

[coderabbitai]

Caution

Failed to replace (edit) comment. This is likely due to insufficient permissions or the comment being deleted.

Error details

{}

[thepastaclaw]

Code Review

The Tenderdash default image bump itself matches the PR goal and points existing defaults at the final 1.6.0 tag. The migration is too broad: it rewrites every persisted Tenderdash image, including documented operator customizations, instead of only upgrading configs still on Dashmate-shipped prerelease tags.

🟡 1 suggestion(s)

🤖 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 `packages/dashmate/configs/getConfigFileMigrationsFactory.js`:
- [SUGGESTION] packages/dashmate/configs/getConfigFileMigrationsFactory.js:1526-1531: Preserve customized Tenderdash images during migration
This migration unconditionally replaces `platform.drive.tenderdash.docker.image` for every config. That upgrades stale defaults, but it also discards explicit operator settings made through the documented Tenderdash image option, such as a private patched image or a local test image. The migration only needs to move configs still using Dashmate-shipped Tenderdash 1.6 prerelease tags to the final base default, matching the preservation approach used by the nearby Envoy image migration.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87.18%. Comparing base (48f0cc3) to head (7a7b212).
⚠️ Report is 1 commits behind head on v3.1-dev.

Additional details and impacted files

@@ Coverage Diff @@## v3.1-dev #3940 +/- ##
==========================================
Coverage 87.17% 87.18% ==========================================
Files 2629 2632 +3 Lines 327221 327563 +342 ==========================================
+ Hits 285265 285592 +327 - Misses 41956 41971 +15 

Components	Coverage Δ
dpp	87.70% <ø> (ø)
drive	86.14% <ø> (ø)
drive-abci	89.45% <ø> (ø)
sdk	∅ <ø> (∅)
dapi-client	∅ <ø> (∅)
platform-version	∅ <ø> (∅)
platform-value	92.20% <ø> (ø)
platform-wallet	∅ <ø> (∅)
drive-proof-verifier	49.55% <ø> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.