-
Notifications
You must be signed in to change notification settings - Fork 839
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[Backport] Version bumps from stable2412-1 + prdocs reorg (#7401)
This PR backports regular version bumps and prdoc reorganization from stable release branch back to master
- Loading branch information
1 parent
0d35be7
commit 698d9ae
Showing
21 changed files
with
42 additions
and
1 deletion.
There are no files selected for viewing
This file contains 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
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
title: 'Fix implication order in implementation of `TransactionExtension` for tuple' | ||
doc: | ||
- audience: | ||
- Runtime Dev | ||
- Runtime User | ||
description: |- | ||
Before this PR, the implications were different in the pipeline `(A, B, C)` and `((A, B), C)`. | ||
This PR fixes this behavior and make nested tuple transparant, the implication order of tuple of | ||
tuple is now the same as in a single tuple. | ||
|
||
For runtime users this mean that the implication can be breaking depending on the pipeline used | ||
in the runtime. | ||
|
||
For runtime developers this breaks usage of `TransactionExtension::validate`. | ||
When calling `TransactionExtension::validate` the implication must now implement `Implication` | ||
trait, you can use `TxBaseImplication` to wrap the type and use it as the base implication. | ||
E.g. instead of `&(extension_version, call),` you can write `&TxBaseImplication((extension_version, call))`. | ||
|
||
crates: | ||
- name: sp-runtime | ||
bump: major | ||
- name: pallet-skip-feeless-payment | ||
bump: major | ||
- name: frame-system | ||
bump: major |
File renamed without changes.
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,16 @@ | ||
# Schema: Polkadot SDK PRDoc Schema (prdoc) v1.0.0 | ||
# See doc at https://raw.githubusercontent.com/paritytech/polkadot-sdk/master/prdoc/schema_user.json | ||
|
||
title: Snowbridge - Support bridging native ETH | ||
|
||
doc: | ||
- audience: Runtime User | ||
description: | ||
Support Native ETH as an asset type instead of only supporting WETH. WETH is still supported, but adds | ||
support for ETH in the inbound and outbound routers. | ||
|
||
crates: | ||
- name: snowbridge-router-primitives | ||
bump: minor | ||
- name: snowbridge-pallet-inbound-queue-fixtures | ||
bump: minor |
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.