Skip to content

[stable2509] Backport #9415#9860

Closed
paritytech-release-backport-bot[bot] wants to merge 1 commit intostable2509from
backport-9415-to-stable2509
Closed

[stable2509] Backport #9415#9860
paritytech-release-backport-bot[bot] wants to merge 1 commit intostable2509from
backport-9415-to-stable2509

Conversation

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

Backport #9415 into stable2509 from kianenigma.

See the documentation on how to use this bot.

Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com>
(cherry picked from commit c40b36c)
@github-actions github-actions Bot added the A3-backport Pull request is already reviewed well in another branch. label Sep 29, 2025
@github-actions github-actions Bot requested a review from kianenigma September 29, 2025 07:26
@sigurpol
Copy link
Copy Markdown
Contributor

already backported - nothing to do, we can discard this one

@sigurpol sigurpol closed this Sep 29, 2025
@github-actions
Copy link
Copy Markdown
Contributor

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.

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