Skip to content

check semver: Update parity-publish v0.10.6 -> v0.10.10#11223

Merged
dmitry-markin merged 7 commits into
masterfrom
dm-fix-semver-check
Mar 2, 2026
Merged

check semver: Update parity-publish v0.10.6 -> v0.10.10#11223
dmitry-markin merged 7 commits into
masterfrom
dm-fix-semver-check

Conversation

@dmitry-markin

@dmitry-markin dmitry-markin commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

Fix failing semver check due to old compiled-in cargo in parity-publish by:

  1. Upgrading parity-publish to the latest version.
  2. Fixing its build dependencies installation with apt-get.
Error: failed to load manifest for workspace member `/__w/polkadot-sdk/polkadot-sdk/bridges/bin/runtime-common`
referenced by workspace at `/__w/polkadot-sdk/polkadot-sdk/Cargo.toml`

Caused by:
    0: failed to load manifest for dependency `bp-header-chain`
    ...
   23: failed to load manifest for dependency `pallet-revive`
   24: failed to parse manifest at `/__w/polkadot-sdk/polkadot-sdk/substrate/frame/revive/Cargo.toml`
   25: feature `edition2024` is required
       
       The package requires the Cargo feature called `edition2024`, but that feature is not stabilized in this version of Cargo (1.83.0).
       Consider adding `cargo-features = ["edition2024"]` to the top of Cargo.toml (above the [package] table) to tell Cargo you are opting in to use this unstable feature.

@dmitry-markin dmitry-markin self-assigned this Mar 2, 2026
@dmitry-markin dmitry-markin requested review from a team as code owners March 2, 2026 09:38
@dmitry-markin dmitry-markin added the R0-no-crate-publish-required The change does not require any crates to be re-published. label Mar 2, 2026
@dmitry-markin

Copy link
Copy Markdown
Contributor Author

Hmm, the env only sets the default toolchain. It looks like we need to use the one present in the image.

@dmitry-markin

Copy link
Copy Markdown
Contributor Author

The check is not using cargo from the toolchain, instead it uses compiled-in cargo in parity-publish.

@dmitry-markin dmitry-markin changed the title check semver: Update nightly toolchain to 2026-03-01 check semver: Update parity-publish v0.10.6 -> v0.10.10 Mar 2, 2026
@dmitry-markin dmitry-markin enabled auto-merge March 2, 2026 11:05
@dmitry-markin dmitry-markin added this pull request to the merge queue Mar 2, 2026
Merged via the queue into master with commit 9636b6d Mar 2, 2026
208 of 212 checks passed
@dmitry-markin dmitry-markin deleted the dm-fix-semver-check branch March 2, 2026 12:25
Kanasjnr pushed a commit to Kanasjnr/polkadot-sdk that referenced this pull request Mar 8, 2026
…1223)

Fix failing semver check due to old compiled-in cargo in parity-publish
by:
1. Upgrading `parity-publish` to the latest version.
2. Fixing its build dependencies installation with `apt-get`.

```
Error: failed to load manifest for workspace member `/__w/polkadot-sdk/polkadot-sdk/bridges/bin/runtime-common`
referenced by workspace at `/__w/polkadot-sdk/polkadot-sdk/Cargo.toml`

Caused by:
    0: failed to load manifest for dependency `bp-header-chain`
    ...
   23: failed to load manifest for dependency `pallet-revive`
   24: failed to parse manifest at `/__w/polkadot-sdk/polkadot-sdk/substrate/frame/revive/Cargo.toml`
   25: feature `edition2024` is required
       
       The package requires the Cargo feature called `edition2024`, but that feature is not stabilized in this version of Cargo (1.83.0).
       Consider adding `cargo-features = ["edition2024"]` to the top of Cargo.toml (above the [package] table) to tell Cargo you are opting in to use this unstable feature.
```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

R0-no-crate-publish-required The change does not require any crates to be re-published.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants