Skip to content

Stabilize V16 metadata #8443

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 7 commits into
base: master
Choose a base branch
from
Open

Stabilize V16 metadata #8443

wants to merge 7 commits into from

Conversation

jsdw
Copy link
Contributor

@jsdw jsdw commented May 6, 2025

This PR bumps frame-metadata 23.0.0, which stabilizes V16 metadata. This was previously available as the "unstable" metadata.

The main additions provided by V16 metadata are:

  • Information about the Pallet View Functions exposed by pallets.
  • Information about the Config associated types used by each pallet.
  • Support for V5 transactions, including support for a chain providing multiple transaction extension versions and multiple supported transaciton versions.
  • Support for deprecation information, so that mostly anything defined in a runtime can be marked as deprecated in order for runtime/pallet authors to communicate to consumers about deprecated items.

To sanity check this, I've built a polkadot node with this change and checked that using Subxt (this PR paritytech/subxt#1999), v16 metadata is indeed available, downloads and decodes correctly.

@jsdw jsdw added R1-breaking_change This PR introduces a breaking change and should be highlighted in the upcoming release. T4-runtime_API This PR/Issue is related to runtime APIs. labels May 6, 2025
@jsdw
Copy link
Contributor Author

jsdw commented May 6, 2025

@bkchr Do you think we should update merkleized-metadata to support frame-metadata@23(which contains the now-stabilized V16 metadata) and then release it prior to merging this PR or after? Given your looser version constraints there we can do things either way around I think!

One constraint is that I'd like to get this merged before the release cutoff date on May 15th to get it into the next stable release, so my preference is to merge this first and update that later.

@jsdw jsdw marked this pull request as ready for review May 6, 2025 13:45
@bkchr
Copy link
Member

bkchr commented May 7, 2025

@bkchr Do you think we should update merkleized-metadata to support frame-metadata@23(which contains the now-stabilized V16 metadata) and then release it prior to merging this PR or after? Given your looser version constraints there we can do things either way around I think!

Given the looser version requirements, no change to merkleized-metadata should be required.

@jsdw
Copy link
Contributor Author

jsdw commented May 8, 2025

Given the looser version requirements, no change to merkleized-metadata should be required.

Makes sense! I guess it will eventually want to be updated for V16 metadata so that it can be used for decoding/checking v5 transactions (because V16 metadata contains the transaction extensions for each possible version the extrinsic might use)?

@paritytech-workflow-stopper
Copy link

All GitHub workflows were cancelled due to failure one of the required jobs.
Failed workflow url: https://github.com/paritytech/polkadot-sdk/actions/runs/14904466681
Failed job name: test-linux-stable

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
R1-breaking_change This PR introduces a breaking change and should be highlighted in the upcoming release. T4-runtime_API This PR/Issue is related to runtime APIs.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants