Allow create backport branches to unstable by A4-backport-unstable* tag#9167
Merged
EgorPopelyaev merged 2 commits intomasterfrom Jul 16, 2025
Merged
Allow create backport branches to unstable by A4-backport-unstable* tag#9167EgorPopelyaev merged 2 commits intomasterfrom
EgorPopelyaev merged 2 commits intomasterfrom
Conversation
bkontur
added
the
R0-no-crate-publish-required
EgorPopelyaev
approved these changes
Jul 16, 2025
Contributor
|
Tested in my fork, fix looks good! |
acatangiu
approved these changes
Jul 16, 2025
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
Contributor
Author
|
nice, looks like it is working: #9237 |
EgorPopelyaev
added a commit
to EgorPopelyaev/polkadot-sdk
that referenced
this pull request
Jul 17, 2025
* Allow create backport branches to unstable by A4-backport-unstable* tag (paritytech#9167) In this [PR](paritytech#9139 (comment)), I added the `A4-backport-unstable2507` label, but no backport branch was created for `unstable2507`. Was this intentional or just an oversight or did I miss anything in the release channel? How do we do backports to unstable2507? If manually, just close this. cc: @EgorPopelyaev - this PR is just a blind draft (not sure if it works), probably more needs to be fixed and properly tested. If we really need this, could you please take it over the finish line? If not, just close it :) Co-authored-by: Egor_P <egor@parity.io> * feat(pallet-xcm): Add supported_version to pallet-xcm genesis config (paritytech#9225) Relates to: polkadot-fellows/runtimes#544 Closes paritytech#9075 Adds a `supported_version` field to the pallet-xcm genesis config. Which allows specifying versioned locations at genesis. * Don't use labels for branch names creation --------- Co-authored-by: Branislav Kontur <bkontur@gmail.com> Co-authored-by: Rodrigo Quelhas <22591718+RomarQ@users.noreply.github.com>
epo-release-automation-app bot
pushed a commit
to EgorPopelyaev/polkadot-sdk
that referenced
this pull request
Jul 17, 2025
* Allow create backport branches to unstable by A4-backport-unstable* tag (paritytech#9167) In this [PR](paritytech#9139 (comment)), I added the `A4-backport-unstable2507` label, but no backport branch was created for `unstable2507`. Was this intentional or just an oversight or did I miss anything in the release channel? How do we do backports to unstable2507? If manually, just close this. cc: @EgorPopelyaev - this PR is just a blind draft (not sure if it works), probably more needs to be fixed and properly tested. If we really need this, could you please take it over the finish line? If not, just close it :) Co-authored-by: Egor_P <egor@parity.io> * feat(pallet-xcm): Add supported_version to pallet-xcm genesis config (paritytech#9225) Relates to: polkadot-fellows/runtimes#544 Closes paritytech#9075 Adds a `supported_version` field to the pallet-xcm genesis config. Which allows specifying versioned locations at genesis. * Don't use labels for branch names creation --------- Co-authored-by: Branislav Kontur <bkontur@gmail.com> Co-authored-by: Rodrigo Quelhas <22591718+RomarQ@users.noreply.github.com> (cherry picked from commit 6e91c9e)
alvicsam
pushed a commit
that referenced
this pull request
Oct 17, 2025
…ag (#9167) In this [PR](#9139 (comment)), I added the `A4-backport-unstable2507` label, but no backport branch was created for `unstable2507`. Was this intentional or just an oversight or did I miss anything in the release channel? How do we do backports to unstable2507? If manually, just close this. cc: @EgorPopelyaev - this PR is just a blind draft (not sure if it works), probably more needs to be fixed and properly tested. If we really need this, could you please take it over the finish line? If not, just close it :) Co-authored-by: Egor_P <egor@parity.io>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In this PR, I added the
A4-backport-unstable2507label, but no backport branch was created forunstable2507.Was this intentional or just an oversight or did I miss anything in the release channel?
How do we do backports to unstable2507? If manually, just close this.
cc: @EgorPopelyaev - this PR is just a blind draft (not sure if it works), probably more needs to be fixed and properly tested. If we really need this, could you please take it over the finish line? If not, just close it :)