Skip to content

ci: Use --locked for cargo doc steps#9828

Merged
lexnv merged 1 commit intomasterfrom
lenxv/locked-docs
Sep 24, 2025
Merged

ci: Use --locked for cargo doc steps#9828
lexnv merged 1 commit intomasterfrom
lenxv/locked-docs

Conversation

@lexnv
Copy link
Copy Markdown
Contributor

@lexnv lexnv commented Sep 24, 2025

This PR adds the --locked option to the cargo doc tests.

Detected by running the CI on PR: https://github.com/paritytech/polkadot-sdk/actions/runs/17972092266/job/51117118432

error[E0277]: the trait bound `BoundedVec<u8, v3::MaxPalletNameLen>: JsonSchema` is not satisfied
   --> polkadot/xcm/src/v3/mod.rs:228:12
    |
228 |     pub name: BoundedVec<u8, MaxPalletNameLen>,
    |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the trait `JsonSchema` is not implemented for `BoundedVec<u8, v3::MaxPalletNameLen>`
    |
note: there are multiple different versions of crate `schemars` in the dependency graph
   --> /usr/local/cargo/registry/src/index.crates.io-1949cf8c6b5b557f/schemars-0.8.22/src/lib.rs:133:1
    |
133 | pub trait JsonSchema {
    | ^^^^^^^^^^^^^^^^^^^^ this is the required trait
    |
   ::: polkadot/xcm/src/v3/junction.rs:49:44
    |
49  | #[cfg_attr(feature = "json-schema", derive(schemars::JsonSchema))]
    |                                            -------- one version of crate `schemars` used here, as a direct dependency of the current crate
    |
   ::: polkadot/xcm/src/lib.rs:31:5

Thanks @bkchr for the suggestion here 🙏

This has been detected while working on:

Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>
@lexnv lexnv requested review from a team as code owners September 24, 2025 10:34
@lexnv lexnv self-assigned this Sep 24, 2025
@lexnv lexnv added the R0-no-crate-publish-required The change does not require any crates to be re-published. label Sep 24, 2025
@lexnv lexnv requested a review from a team September 24, 2025 10:36
@paritytech-review-bot paritytech-review-bot bot requested a review from a team September 24, 2025 10:43
@bkchr bkchr added this pull request to the merge queue Sep 24, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Sep 24, 2025
@lexnv lexnv added this pull request to the merge queue Sep 24, 2025
Merged via the queue into master with commit 80ee9c8 Sep 24, 2025
257 of 263 checks passed
@lexnv lexnv deleted the lenxv/locked-docs branch September 24, 2025 15:34
alvicsam pushed a commit that referenced this pull request Oct 17, 2025
This PR adds the `--locked` option to the cargo doc tests.

Detected by running the CI on PR:
https://github.com/paritytech/polkadot-sdk/actions/runs/17972092266/job/51117118432

```rust
error[E0277]: the trait bound `BoundedVec<u8, v3::MaxPalletNameLen>: JsonSchema` is not satisfied
   --> polkadot/xcm/src/v3/mod.rs:228:12
    |
228 |     pub name: BoundedVec<u8, MaxPalletNameLen>,
    |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the trait `JsonSchema` is not implemented for `BoundedVec<u8, v3::MaxPalletNameLen>`
    |
note: there are multiple different versions of crate `schemars` in the dependency graph
   --> /usr/local/cargo/registry/src/index.crates.io-1949cf8c6b5b557f/schemars-0.8.22/src/lib.rs:133:1
    |
133 | pub trait JsonSchema {
    | ^^^^^^^^^^^^^^^^^^^^ this is the required trait
    |
   ::: polkadot/xcm/src/v3/junction.rs:49:44
    |
49  | #[cfg_attr(feature = "json-schema", derive(schemars::JsonSchema))]
    |                                            -------- one version of crate `schemars` used here, as a direct dependency of the current crate
    |
   ::: polkadot/xcm/src/lib.rs:31:5
```

Thanks @bkchr for the suggestion here 🙏 

This has been detected while working on:
- #9418

Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>
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.

5 participants