Skip to content

Don't use labels for branch creation#83

Merged
EgorPopelyaev merged 3 commits intomasterfrom
ep-fix-backport-pipeline
Jul 17, 2025
Merged

Don't use labels for branch creation#83
EgorPopelyaev merged 3 commits intomasterfrom
ep-fix-backport-pipeline

Conversation

@EgorPopelyaev
Copy link
Copy Markdown
Owner

No description provided.

bkontur and others added 3 commits July 16, 2025 16:23
…ag (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 <[email protected]>
…aritytech#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.
@EgorPopelyaev EgorPopelyaev merged commit 6e91c9e into master Jul 17, 2025
6 of 8 checks passed
@epo-release-automation-app
Copy link
Copy Markdown

Created backport PR for stable2503:

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

git fetch origin backport-83-to-stable2503
git worktree add --checkout .worktree/backport-83-to-stable2503 backport-83-to-stable2503
cd .worktree/backport-83-to-stable2503
git reset --hard HEAD^
git cherry-pick -x 6e91c9e30df79966c2deec770b75474d7fd0e8e7
git push --force-with-lease

epo-release-automation-app bot pushed a commit 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 <[email protected]>

* 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 <[email protected]>
Co-authored-by: Rodrigo Quelhas <[email protected]>
(cherry picked from commit 6e91c9e)
@epo-release-automation-app
Copy link
Copy Markdown

Successfully created backport PR for unstable2507:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants