Bump subxt-utils-fetchmetadata from 0.44.0 to 0.50.3 in /tools/runtime-codegen

[dependabot]

Bumps subxt-utils-fetchmetadata from 0.44.0 to 0.50.3.

Release notes

Sourced from subxt-utils-fetchmetadata's releases.

v0.50.3

This release updates frame-decode to 0.18.1, which fixes V5 signer payload construction and improves how authorization extensions (like VerifyMultiSignature) are handled.

Fixed

• V5 signer payloads now correctly include the transaction extension version and call data as an immutable base implication, matching FRAME's transaction extension pipeline semantics. (paritytech/frame-decode#104)
• Unknown Option<T> transaction extensions are now encoded as None (0u8) by default, allowing transaction encoding to succeed on chains with optional extensions. (from frame-decode 0.17.2)

Changed

• VerifySignature now uses is_authorization_extension to declare itself as an authorization boundary, replacing the previous out.clear() side effects in encode_value_for_signer_payload_to and encode_implicit_to. (#2268, #2269)
• Update frame-decode from 0.17.1 to 0.18.1. (#2268)

v0.50.0

[0.50.0] - 2025-12-17

This release version is a deliberately large bump up from 0.44.0 to signify the extent of the changes in this release.

The headline changes are as follows:

• Subxt is no longer head-of-chain only, and can work with historic blocks, all the way back to genesis. Note: user-provided type information is required to do this for very old (> ~2year old, ie pre-V14 metadata) blocks.
• The MVP subxt-historic crate has been removed, its functionality having been merged into Subxt.
• The subxt-core crate has been removed for now to make way for the above. Subxt itself continues to support WASM use cases.
  • For truly no-std functionality, the frame-decode crate now contains much of the underlying logic used throughout Subxt to encode and decode things, and we would like to expand the functionality here.
  • We would like feedback from any users of the subxt-core crate on how they use it, and will use this feedback to drive future work in this area.
• No more monitoring for runtime updates is needed; Subxt now works across different runtime versions automatically.
• Errors are no longer one big Error enum; instead different Subxt APIs return different errors, to limit the number of possible errors in any one place. These all convert into subxt::Error so this can continue to be used as a catch-all.
• Storage APIs have been redone, fixing some issues and giving much more control over iteration, as well as key and value decoding.

There are also a couple of organizational changes which aren't visible:

• We now follow the name.rs + name/submodule.rs convention instead of the name/mod.rs + name/submodule.rs convention.
• CI and testing updates hopefully ensure better organization and coverage with a greater number of different feature flags being tested.

This changes have results in many breaking changes across APIs, which I will try my best to summarize below.

A good place to look for a more holistic understanding of what's changes are the examples, both:

• The smaller single-file examples
• The larger project-based examples

For the smaller examples, start with the basic transaction submission example and then have a look at the blocks example and the storage example to give the best broad overview of the changes. Pick and choose others next depending on what suits.

A breakdown of the significant changes follows, to aid migration efforts:

Configuration

Before

Configuration (PolkadotConfig and SubstrateConfig) was type-only and didn't exist at the value level, and so you'd provide it to the client like so:

use subxt::{OnlineClient, PolkadotConfig};
</tr></table> 

... (truncated)

Changelog

Sourced from subxt-utils-fetchmetadata's changelog.

[0.50.3] - 2026-08-06

This release updates frame-decode to 0.18.1, which fixes V5 signer payload construction and improves how authorization extensions (like VerifyMultiSignature) are handled.

Fixed

• V5 signer payloads now correctly include the transaction extension version and call data as an immutable base implication, matching FRAME's transaction extension pipeline semantics. (paritytech/frame-decode#104)
• Unknown Option<T> transaction extensions are now encoded as None (0u8) by default, allowing transaction encoding to succeed on chains with optional extensions. (from frame-decode 0.17.2)

Changed

• VerifySignature now uses is_authorization_extension to declare itself as an authorization boundary, replacing the previous out.clear() side effects in encode_value_for_signer_payload_to and encode_implicit_to. (#2268, #2269)
• Update frame-decode from 0.17.1 to 0.18.1. (#2268)

[0.50.2] - 2026-07-06

This release fixes an issue whereby setting the genesis hash in the SubstrateConfigBuilder had no effect, and improves the reliability of tests against public archival RPC endpoints.

Changed

• Update Artifacts (auto-generated) (#2245)
• tests: Exponential backoff for archival RPC public endpoints (#2244)

Fixed

• Fix: SubstrateConfigBuilder::set_genesis_hash is a no-op (#2236)

[0.50.1] - 2026-04-27

This release bumps the light-client smoldot crate to the latest version and adds several fixes.

Changed

• Bump smoldot (#2217)
• Update rust version (#2218)

Fixed

• Fix clippy (#2226)
• VerifySignature => VerifyMultiSignature tx extension rename to fix (#2197)
• chore: fix some minor issues in the comments (#2211)

[0.50.0] - 2025-12-17

This release version is a deliberately large bump up from 0.44.0 to signify the extent of the changes in this release.

The headline changes are as follows:

• Subxt is no longer head-of-chain only, and can work with historic blocks, all the way back to genesis. Note: user-provided type information is required to do this for very old (> ~2year old, ie pre-V14 metadata) blocks.
• The MVP subxt-historic crate has been removed, its functionality having been merged into Subxt.
• The subxt-core crate has been removed for now to make way for the above. Subxt itself continues to support WASM use cases.

... (truncated)

Commits

• 49ea25d chore: bump version to 0.50.3 (#2270)
• 3823937 build(deps): update frame-decode to 0.18.1 (#2268)
• e2b7360 fix: don't keep the startup finalized block pinned forever (#2266)
• a3254e5 feat: decode call data into dynamic transaction payload (#2262)
• 9103668 build(deps): bump keccak in /testing/wasm-lightclient-tests (#2261)
• 58e3121 build(deps): bump actions/setup-node from 4 to 7 (#2258)
• 1a4ecb0 build(deps): bump actions/setup-node from 4 to 7 in /.github/workflows (#2259)
• c62ba94 Update Artifacts (auto-generated) (#2260)
• 6f86195 ci: promote lightclient test jobs from flaky to mandatory (#2257)
• 80ca989 ci: Set github action identity for updating artifacts (#2256)
• Additional commits viewable in compare view

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	subxt-utils-fetchmetadata@​0.44.0 ⏵ 0.50.3

View full report