Skip to content

[stable2512] Backport #10680#10684

Closed
paritytech-release-backport-bot[bot] wants to merge 1 commit intostable2512from
backport-10680-to-stable2512
Closed

[stable2512] Backport #10680#10684
paritytech-release-backport-bot[bot] wants to merge 1 commit intostable2512from
backport-10680-to-stable2512

Conversation

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

Backport #10680 into stable2512 from pgherveou.

See the documentation on how to use this bot.

Fix post_upgrade assertion logic in revive v2 migration

---------

Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com>
(cherry picked from commit 95b300f)
@github-actions github-actions Bot added the A3-backport Pull request is already reviewed well in another branch. label Dec 17, 2025
@github-actions github-actions Bot requested a review from pgherveou December 17, 2025 15:53
@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.

@athei athei closed this Dec 17, 2025
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