Skip to content

[stable2503] Backport #8140#8147

Merged
EgorPopelyaev merged 1 commit intostable2503from
backport-8140-to-stable2503
Apr 3, 2025
Merged

[stable2503] Backport #8140#8147
EgorPopelyaev merged 1 commit intostable2503from
backport-8140-to-stable2503

Conversation

@paritytech-release-backport-bot

Backport #8140 into stable2503 from ggwpez.

See the documentation on how to use this bot.

Prdocs for:
- #7598
- #7620
- #7627
- more?

---------

Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io>
(cherry picked from commit f238dce)
@github-actions github-actions bot added the A3-backport Pull request is already reviewed well in another branch. label Apr 3, 2025
@github-actions github-actions bot requested a review from ggwpez April 3, 2025 10:45
@github-actions
Copy link
Contributor

github-actions bot commented Apr 3, 2025

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.

@EgorPopelyaev EgorPopelyaev merged commit b9a4329 into stable2503 Apr 3, 2025
236 of 258 checks passed
@EgorPopelyaev EgorPopelyaev deleted the backport-8140-to-stable2503 branch April 3, 2025 11:17
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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants