docs: dev blog posts for 2617 distribution#3218
Merged
Merged
Conversation
Test Results 5 files 203 suites 57m 17s ⏱️ Results for commit a81064d. ♻️ This comment has been updated with latest results. |
jpraynaud
temporarily deployed
to
testing-preview
April 21, 2026 16:36 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
Alenar
approved these changes
Apr 22, 2026
olgahryniuk
approved these changes
Apr 22, 2026
jpraynaud
temporarily deployed
to
testing-preview
April 22, 2026 11:01 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
jpraynaud
force-pushed
the
jpraynaud/2967-dev-blog-posts-2617
branch
from
April 22, 2026 12:51
7d2b909 to
7f21ce1
Compare
jpraynaud
temporarily deployed
to
testing-preview
April 22, 2026 13:11 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
… post for '2617.0' distribution
… post for '2617.0' distribution
Co-authored-by: olgahryniuk <olgahryniuk@users.noreply.github.com>
jpraynaud
force-pushed
the
jpraynaud/2967-dev-blog-posts-2617
branch
from
April 28, 2026 09:25
7f21ce1 to
9a6daae
Compare
jpraynaud
force-pushed
the
jpraynaud/2967-dev-blog-posts-2617
branch
from
April 28, 2026 09:27
9a6daae to
a81064d
Compare
jpraynaud
temporarily deployed
to
testing-preview
April 28, 2026 09:45 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
jpraynaud
marked this pull request as ready for review
April 28, 2026 12:58
There was a problem hiding this comment.
Pull request overview
Adds and updates dev blog content for the Mithril 2617 distribution, aligning the website announcements and several ongoing testing-program posts with the latest release status.
Changes:
- Add three new dev blog posts for distribution
2617(distribution announcement, signer1.0.0stable release, static builds). - Update several existing dev blog posts to reflect
2617.0rollout progress (DMQ + multiple aggregators testing programs; client CLI backend decommission note). - Update the website announcement bar messaging to reflect production-ready signer status.
Reviewed changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
| docs/website/docusaurus.config.js | Updates the announcement bar CTA messaging for SPOs. |
| docs/website/blog/2026-04-28-static-builds.md | New post describing static builds, feature/allocator defaults, and Docker base image updates. |
| docs/website/blog/2026-04-28-mithril-signer-stable-release.md | New post announcing signer 1.0.0 as production-ready and providing upgrade instructions. |
| docs/website/blog/2026-04-28-distribution-2617.md | New post announcing distribution 2617.0, key changes, and operator upgrade guidance. |
| docs/website/blog/2026-01-06-multiple-aggregators-testing-program.md | Adds an update section and extends the rollout plan through 2617.0. |
| docs/website/blog/2026-01-06-dmq-testing-program.md | Adds an update section and extends the rollout plan through 2617.0 (+ adjustments to milestone numbering). |
| docs/website/blog/2025-06-17-client-cli-cardano-database-backends.md | Updates the timeline to mark v1 backend removed as of distribution 2617.0. |
| ::: | ||
|
|
||
| - **Mithril signer stable release**: bumped the Mithril signer to version `1.0.0`, marking it as **production-ready** on the `release-mainnet` network | ||
| - **Cardano node support**: added support for Cardano node `10.6.2` and `10.7.1` in the signer, aggregator, and client |
There was a problem hiding this comment.
The Cardano node support bullet appears to overstate client support. CHANGELOG.md lists 10.6.2 support for signer+aggregator, and 10.7.1 support for signer+aggregator+client; consider splitting this into two bullets (or rewording) to avoid implying the client supports 10.6.2 as well.
Suggested change
| - **Cardano node support**: added support for Cardano node `10.6.2` and `10.7.1` in the signer, aggregator, and client | |
| - **Cardano node support**: added support for Cardano node `10.6.2` in the signer and aggregator | |
| - **Cardano node support**: added support for Cardano node `10.7.1` in the signer, aggregator, and client |
Comment on lines
+21
to
+23
| - **Release process**: upgraded the release process to support synchronization with Cardano node releases | ||
| - **Removed**: the `v1` backend of Cardano database is removed from the client CLI and library | ||
| - **Preliminary support for Cardano blocks and transactions certification**: storage of Cardano blocks in the signer and aggregator `cardano_tx` SQLite database |
There was a problem hiding this comment.
The "Removed" bullet is a bit redundant/awkward ("Removed: ... is removed"). Rewording this would improve readability (e.g., "has been removed" or drop one of the "removed" occurrences).
Comment on lines
+10
to
+14
| With the [`2617.0`](https://github.com/input-output-hk/mithril/releases/tag/2617.0) distribution, all Mithril nodes are now statically built in the CI pipelines. This significantly simplifies deployment and removes a long-standing portability constraint. | ||
|
|
||
| #### What has changed? | ||
|
|
||
| - The aggregator, signer, client, and relay are statically built on both the GitHub and Hydra CI pipelines using the `musl` target |
There was a problem hiding this comment.
This states the relay is statically built on Hydra CI via musl, but the Nix flake only defines musl builds for mithril-aggregator, mithril-signer, and mithril-client-cli (no mithril-relay, and musl is only enabled for x86_64-linux). Either adjust this statement to match what Hydra actually builds, or add the missing relay musl package to the Hydra/Nix pipeline.
Suggested change
| With the [`2617.0`](https://github.com/input-output-hk/mithril/releases/tag/2617.0) distribution, all Mithril nodes are now statically built in the CI pipelines. This significantly simplifies deployment and removes a long-standing portability constraint. | |
| #### What has changed? | |
| - The aggregator, signer, client, and relay are statically built on both the GitHub and Hydra CI pipelines using the `musl` target | |
| With the [`2617.0`](https://github.com/input-output-hk/mithril/releases/tag/2617.0) distribution, Mithril binaries are now statically built in the CI pipelines. This significantly simplifies deployment and removes a long-standing portability constraint. | |
| #### What has changed? | |
| - The aggregator, signer, and client are statically built on the Hydra CI pipeline using the `musl` target on `x86_64-linux`; GitHub CI also produces static builds for Mithril nodes, including the relay |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Content
This PR includes the dev blog posts for the
2617Mithril distribution:2617is now available blog post.1.0.0stable release blog post.Pre-submit checklist
Issue(s)
Relates to #2967