Skip to content

Commit

Permalink
[Backport] Version bumps from stable2412-1 + prdocs reorg (#7401)
Browse files Browse the repository at this point in the history
This PR backports regular version bumps and prdoc reorganization from
stable release branch back to master
  • Loading branch information
EgorPopelyaev authored Jan 31, 2025
1 parent 0d35be7 commit 698d9ae
Show file tree
Hide file tree
Showing 21 changed files with 42 additions and 1 deletion.
2 changes: 1 addition & 1 deletion polkadot/node/primitives/src/lib.rs
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@ pub use disputes::{
/// relatively rare.
///
/// The associated worker binaries should use the same version as the node that spawns them.
pub const NODE_VERSION: &'static str = "1.17.0";
pub const NODE_VERSION: &'static str = "1.17.1";

// For a 16-ary Merkle Prefix Trie, we can expect at most 16 32-byte hashes per node
// plus some overhead:
Expand Down
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.
25 changes: 25 additions & 0 deletions prdoc/stable2412-1/pr_7067.prdoc
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.
16 changes: 16 additions & 0 deletions prdoc/stable2412-1/pr_7090.prdoc
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.

0 comments on commit 698d9ae

Please sign in to comment.