Skip to content

[unstable2507] Backport #83#85

Closed
epo-release-automation-app[bot] wants to merge 1 commit intounstable2507from
backport-83-to-unstable2507
Closed

[unstable2507] Backport #83#85
epo-release-automation-app[bot] wants to merge 1 commit intounstable2507from
backport-83-to-unstable2507

Conversation

@epo-release-automation-app
Copy link
Copy Markdown

Backport #83 into unstable2507 from EgorPopelyaev.

See the documentation on how to use this bot.

* 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)
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.

1 participant