Merge pull request #2396 from input-output-hk/jpraynaud/2332-dev-blog-post-distribution-2513

Docs: add dev blog post for distribution `2513`

Author: jpraynaud

docs/website/blog/2025-03-28-distribution-2513.md

@@ -0,0 +1,34 @@
+---
+title: Distribution `2513` is now available
+authors:
+  - name: Mithril Team
+tags: [release, distribution, 2513, security-advisory]
+---
+
+### Distribution `2513` is now available
+
+The [`2513.0`](https://github.com/input-output-hk/mithril/releases/tag/2513.0) distribution has been released, introducing the following changes:
+
+- ⚠️ **Breaking** changes in Mithril nodes:
+  - The **minimum required** `glibc` version for pre-built Linux binaries has been upgraded from `2.31` to `2.35`
+  - Mithril signers running versions `<=0.2.200` **must be updated** due to the removal of Thales era legacy code
+  - The `with_snapshot_uploader` function in the Mithril client library has been renamed to `with_file_uploader`
+- Added support for Cardano node `10.2.1` in the signer and aggregator
+- Ended support for **macOS x64 pre-built binaries** for the client CLI
+- Bug fixes and performance improvements.
+
+This new distribution has been deployed to the **Mithril aggregator** on the `release-mainnet` and `release-preprod` networks.
+
+If you are running a **Mithril signer**:
+
+- **pre-release-preview** network: no action is required at this time
+- **release-preprod** network: upgrade your signer node binary to version `0.2.237` – no configuration updates are required
+- **release-mainnet** network: upgrade your signer node binary to version `0.2.237`– no configuration updates are required.
+
+You can update the Mithril signer using the one-line command below. It downloads to the current directory by default, but you can specify a custom folder using the -p option:
+
+```bash
+curl --proto '=https' --tlsv1.2 -sSf https://raw.githubusercontent.com/input-output-hk/mithril/refs/heads/main/mithril-install.sh | sh -s -- -c mithril-signer -d 2513.0 -p $(pwd)
+```
+
+For any inquiries or assistance, contact the team on the [Discord channel](https://discord.gg/5kaErDKDRq).