Skip to content
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

Backport/2412: Expose the unstable metadata v16 #6676

Merged
merged 3 commits into from
Nov 27, 2024

Conversation

lexnv
Copy link
Contributor

@lexnv lexnv commented Nov 27, 2024

This PR is a backport for:

cc @paritytech/subxt-team

@lexnv lexnv added the A3-backport Pull request is already reviewed well in another branch. label Nov 27, 2024
@lexnv lexnv self-assigned this Nov 27, 2024
@lexnv lexnv requested review from a team and koute as code owners November 27, 2024 13:55
Signed-off-by: Alexandru Vasile <[email protected]>
@lexnv lexnv requested a review from EgorPopelyaev November 27, 2024 13:57
Copy link

This pull request is amending an existing release. Please proceed with extreme caution,
as to not impact downstream teams that rely on the stability of it. Some things to consider:

  • Backports are only for 'patch' or 'minor' changes. No 'major' or other breaking change.
  • Should be a legit fix for some bug, not adding tons of new features.
  • Must either be already audited or not need an audit.
Emergency Bypass

If you really need to bypass this check: add validate: false to each crate
in the Prdoc where a breaking change is introduced. This will release a new major
version of that crate and all its reverse dependencies and basically break the release.

@EgorPopelyaev EgorPopelyaev merged commit e607de0 into stable2412 Nov 27, 2024
49 of 50 checks passed
@EgorPopelyaev EgorPopelyaev deleted the lexnv/backport-v16 branch November 27, 2024 16:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A3-backport Pull request is already reviewed well in another branch.
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

3 participants