Skip to content

[stable2512] Backport #11433#11439

Open
paritytech-release-backport-bot[bot] wants to merge 3 commits intostable2512from
backport-11433-to-stable2512
Open

[stable2512] Backport #11433#11439
paritytech-release-backport-bot[bot] wants to merge 3 commits intostable2512from
backport-11433-to-stable2512

Conversation

@paritytech-release-backport-bot

Backport #11433 into stable2512 from EgorPopelyaev.

See the documentation on how to use this bot.

This PR adds option to publish crates in parallel to the Publish Crates
flow

(cherry picked from commit fa14a5a)
@github-actions
Copy link
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.

Add GITHUB_TOKEN to push release branch on failure.
@EgorPopelyaev EgorPopelyaev added the R0-no-crate-publish-required The change does not require any crates to be re-published. label Mar 19, 2026
@paritytech-review-bot paritytech-review-bot bot requested a review from a team March 19, 2026 17:21
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.

2 participants