Skip to content

[stable2512] Backport #10419 #10432

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 2 commits into
base: stable2512
Choose a base branch
from
Open

[stable2512] Backport #10419 #10432

wants to merge 2 commits into from

Conversation

@paritytech-release-backport-bot
Copy link

@paritytech-release-backport-bot paritytech-release-backport-bot bot commented Nov 26, 2025

Backport #10419 into stable2512 from EgorPopelyaev.

See the documentation on how to use this bot.

@EgorPopelyaev @github-actions
[Release|CI/CD] Send release notifications to communication channels …
59ed69d 
…only in case of a stable release (#10419)

Closes: paritytech/devops#3831
(cherry picked from commit 49bd017)
@paritytech-release-backport-bot paritytech-release-backport-bot bot mentioned this pull request Nov 26, 2025
Merged
@github-actions github-actions bot added the A3-backport Pull request is already reviewed well in another branch. label Nov 26, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Nov 26, 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 enabled auto-merge (squash) November 26, 2025 08:22
@EgorPopelyaev EgorPopelyaev added the R0-no-crate-publish-required The change does not require any crates to be re-published. label Nov 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@EgorPopelyaev EgorPopelyaev Awaiting requested review from EgorPopelyaev

Assignees

No one assigned

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

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@EgorPopelyaev