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

ci: Update deny.toml to reflect the latest changes #83

Merged
merged 4 commits into from
Oct 9, 2024
Merged

Conversation

lexnv
Copy link
Contributor

@lexnv lexnv commented Sep 26, 2024

For more details check: EmbarkStudios/cargo-deny#611

cc @paritytech/subxt-team

@lexnv lexnv self-assigned this Sep 26, 2024
Signed-off-by: Alexandru Vasile <[email protected]>
Signed-off-by: Alexandru Vasile <[email protected]>
Comment on lines +94 to +111
[graph]
# If 1 or more target triples (and optionally, target_features) are specified, only
# the specified targets will be checked when running `cargo deny check`. This means,
# if a particular package is only ever used as a target specific dependency, such
# as, for example, the `nix` crate only being used via the `target_family = "unix"`
# configuration, that only having windows targets in this list would mean the nix
# crate, as well as any of its exclusive dependencies not shared by any other
# crates, would be ignored, as the target list here is effectively saying which
# targets you are building for.
targets = [
# The triple can be any string, but only the target triples built in to
# rustc (as of 1.40) can be checked against actual config expressions
#{ triple = "x86_64-unknown-linux-musl" },
# You can also specify which target_features you promise are enabled for a particular
# target. target_features are currently not validated against the actual valid
# features supported by the target architecture.
#{ triple = "wasm32-unknown-unknown", features = ["atomics"] },
]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess this is just kept to document the feature?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's probably copy-pasted from the template that cargo-deny generates

bkontur added a commit to paritytech/parity-bridges-common that referenced this pull request Oct 4, 2024
bkontur added a commit to paritytech/parity-bridges-common that referenced this pull request Oct 7, 2024
… support (#3059)

* Add `LaneId` generic param

* Version

* Update testnet runtimes

* New polkadot-sdk version

* Removed unnecessary `type LaneId`

* 1.7.10 -> 1.7.0

* change bullseye?

* fix test

* I have no idea, inspired by paritytech/frame-metadata#83

* Bump master polkadot-sdk

* Fix clippy for new rustc - next regeneration should be fixed when paritytech/subxt#1814 is released

* Switch clippy from nightly to stable, because of nalgebra deps hangs 6hours: rust-lang/rust#130056 and also polkadot-sdk is using stable for clippy and doc:
https://gitlab.parity.io/parity/mirrors/parity-bridges-common/-/jobs/7515555
https://gitlab.parity.io/parity/mirrors/parity-bridges-common/-/jobs/7515561
@lexnv lexnv merged commit 50d42be into main Oct 9, 2024
9 checks passed
@lexnv lexnv deleted the lexnv/fix-deny-ci branch October 9, 2024 14:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants