Skip to content
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.

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

[stable2409] Backport #6323 #6472

Conversation

paritytech-cmd-bot-polkadot-sdk[bot]

Backport #6323 into stable2409 from gui1117.

See the documentation on how to use this bot.

@paritytech-cmd-bot-polkadot-sdk
Copy link
Author

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin backport-6323-to-stable2409
git worktree add --checkout .worktree/backport-6323-to-stable2409 backport-6323-to-stable2409
cd .worktree/backport-6323-to-stable2409
git reset --hard HEAD^
git cherry-pick -x 8e3d929623d43398ed3ab8c9ca813aff32588011
git push --force-with-lease

@gui1117
Copy link
Contributor

gui1117 commented Nov 13, 2024

backport only to 2412

@gui1117 gui1117 closed this Nov 13, 2024
@gui1117 gui1117 deleted the backport-6323-to-stable2409 branch November 13, 2024 23:58
Copy link

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