Skip to content

[unstable2507] Backport #9201#9542

Closed
paritytech-release-backport-bot[bot] wants to merge 4 commits intounstable2507from
backport-9201-to-unstable2507
Closed

[unstable2507] Backport #9201#9542
paritytech-release-backport-bot[bot] wants to merge 4 commits intounstable2507from
backport-9201-to-unstable2507

Conversation

@paritytech-release-backport-bot
Copy link
Copy Markdown

Backport #9201 into unstable2507 from iulianbarbu.

See the documentation on how to use this bot.

…#9201)

# Description

- log::info! the error of accessing `GetParachainInfo::parachain_id()`
runtime api if any, before reading the `para_id` from the chain
specification (relevant for debugging).
- removes comments/deprecation notices throughout the code that
introduce `para-id` flag removal (from chain-spec-builder and support
for parsing it from chain specifications)

Closes #9217

## Integration

N/A

## Review Notes

N/A

---------

Signed-off-by: Iulian Barbu <iulian.barbu@parity.io>
Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Sebastian Kunert <mail@skunert.dev>
Co-authored-by: Andrei Sandu <54316454+sandreim@users.noreply.github.com>
(cherry picked from commit 2660bf5)
@iulianbarbu
Copy link
Copy Markdown
Contributor

Check publish compile fails here. The error looks different from the previous errors of the PRs against master. This seems to have been the case for other backports that were merged in unstable2507 before. Is this a known issue, or it should be investigated/fixed?

@iulianbarbu
Copy link
Copy Markdown
Contributor

Seems like latest backport PR merged in unstabe2507 suffered from same fate: https://github.com/paritytech/polkadot-sdk/actions/runs/17725056530/job/50364276349. @EgorPopelyaev any idea why? Probably this will impact the crates releasing based on this branch, but maybe you know better if this failure is really an issue. LMK, otherwise we can merge this.

@bkchr bkchr closed this Feb 4, 2026
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

None yet

Development

Successfully merging this pull request may close these issues.

3 participants