Skip to content

Conversation

@paritytech-release-backport-bot

Backport #10268 into unstable2507 from alvicsam.

See the documentation on how to use this bot.

@paritytech-release-backport-bot
Copy link
Author

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

git fetch origin backport-10268-to-unstable2507
git worktree add --checkout .worktree/backport-10268-to-unstable2507 backport-10268-to-unstable2507
cd .worktree/backport-10268-to-unstable2507
git reset --hard HEAD^
git cherry-pick -x 73de3bed249afc8ed48b0b69be27a0ee063086a3
git push --force-with-lease

@github-actions github-actions bot added the A3-backport Pull request is already reviewed well in another branch. label Nov 10, 2025
@github-actions github-actions bot requested a review from alvicsam November 10, 2025 17:50
@EgorPopelyaev EgorPopelyaev added the R0-no-crate-publish-required The change does not require any crates to be re-published. label Nov 10, 2025
EgorPopelyaev and others added 2 commits November 11, 2025 10:19
This reverts commit a3b4fe6.
Our mac runners have bash version 3.x, fixing by installing cargo
manually.
fix paritytech/devops#4514
@EgorPopelyaev EgorPopelyaev marked this pull request as ready for review November 11, 2025 09:21
@EgorPopelyaev EgorPopelyaev requested review from a team as code owners November 11, 2025 09:21
@EgorPopelyaev EgorPopelyaev enabled auto-merge (squash) November 11, 2025 09:22
@paritytech-review-bot paritytech-review-bot bot requested a review from a team November 11, 2025 09:22
@EgorPopelyaev EgorPopelyaev merged commit 8a611c5 into unstable2507 Nov 11, 2025
475 of 500 checks passed
@EgorPopelyaev EgorPopelyaev deleted the backport-10268-to-unstable2507 branch November 11, 2025 10:50
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.

3 participants