Skip to content

[stable2603] Backport #10976#11238

Merged
DenzelPenzel merged 2 commits intostable2603from
backport-10976-to-stable2603
Mar 5, 2026
Merged

[stable2603] Backport #10976#11238
DenzelPenzel merged 2 commits intostable2603from
backport-10976-to-stable2603

Conversation

@paritytech-release-backport-bot
Copy link
Copy Markdown

Backport #10976 into stable2603 from DenzelPenzel.

See the documentation on how to use this bot.

@paritytech-release-backport-bot
Copy link
Copy Markdown
Author

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin backport-10976-to-stable2603
git worktree add --checkout .worktree/backport-10976-to-stable2603 backport-10976-to-stable2603
cd .worktree/backport-10976-to-stable2603
git reset --hard HEAD^
git cherry-pick -x 13aca011ecc3184fcaa853526169381104b4c4e3
git push --force-with-lease

@github-actions github-actions Bot added the A3-backport Pull request is already reviewed well in another branch. label Mar 3, 2026
@github-actions github-actions Bot requested a review from DenzelPenzel March 3, 2026 12:42
Implemented #10944

Changes:
- Add storage state metrics (statement count, byte usage, capacity
utilization)
- Add network/gossip metrics (connected peers, received statements)

(cherry picked from commit 13aca01)
@DenzelPenzel DenzelPenzel force-pushed the backport-10976-to-stable2603 branch from 317aa72 to db34eec Compare March 3, 2026 13:33
@DenzelPenzel DenzelPenzel marked this pull request as ready for review March 3, 2026 13:37
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Mar 3, 2026

This pull request is amending an existing release. Please proceed with extreme caution,
as to not impact downstream teams that rely on the stability of it. Some things to consider:

  • Backports are only for 'patch' or 'minor' changes. No 'major' or other breaking change.
  • Should be a legit fix for some bug, not adding tons of new features.
  • Must either be already audited or not need an audit.
Emergency Bypass

If you really need to bypass this check: add validate: false to each crate
in the Prdoc where a breaking change is introduced. This will release a new major
version of that crate and all its reverse dependencies and basically break the release.

@DenzelPenzel DenzelPenzel enabled auto-merge (squash) March 4, 2026 09:31
@alexggh alexggh added the R0-no-crate-publish-required The change does not require any crates to be re-published. label Mar 5, 2026
@DenzelPenzel DenzelPenzel merged commit 928ed64 into stable2603 Mar 5, 2026
264 of 274 checks passed
@DenzelPenzel DenzelPenzel deleted the backport-10976-to-stable2603 branch March 5, 2026 12:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A3-backport Pull request is already reviewed well in another branch. R0-no-crate-publish-required The change does not require any crates to be re-published.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants