Skip to content

[stable2603] Backport #11632#11681

Open
paritytech-release-backport-bot[bot] wants to merge 1 commit intostable2603from
backport-11632-to-stable2603
Open

[stable2603] Backport #11632#11681
paritytech-release-backport-bot[bot] wants to merge 1 commit intostable2603from
backport-11632-to-stable2603

Conversation

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

Backport #11632 into stable2603 from BDevParity.

See the documentation on how to use this bot.

)

paritytech/release-engineering#291

TODO:
- handle warnings on all workflows regarding deprecated Node version 20

(cherry picked from commit b0afea2)
@github-actions github-actions bot added the A3-backport Pull request is already reviewed well in another branch. label Apr 7, 2026
@github-actions github-actions bot requested a review from BDevParity April 7, 2026 17:03
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 7, 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.

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.

1 participant