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

chore: Fix cargo-deny configuration #9

Merged
merged 4 commits into from
Oct 13, 2024
Merged

chore: Fix cargo-deny configuration #9

merged 4 commits into from
Oct 13, 2024

Conversation

DataTriny
Copy link
Member

Blocks #7

This makes cargo-deny stricter, but also more in line with the rest of the ecosystem.

@mwcampbell
Copy link
Contributor

How much of this will we be applying to the main repo? Of course, this is the kind of thing that's annoying to maintain across multiple repos. But I think we had to do that split.

@DataTriny
Copy link
Member Author

@mwcampbell I plan to basically copy this into the main repo, which will fix AccessKit/accesskit#349. We will be able to clean deny.toml a bit once AccessKit/accesskit#456 lands.

@DataTriny
Copy link
Member Author

So it would make more sense to merge the zbus 4 PR first.

@DataTriny
Copy link
Member Author

Here is the reason for the skipped dependencies:

  • event-listener and event-listener-strategy: old async-channel version,
  • syn: old thiserror version

In all cases we could get rid of them by updating the old crates in Cargo.lock.

@DataTriny
Copy link
Member Author

This should be ready now.

@mwcampbell mwcampbell merged commit 5cc7729 into main Oct 13, 2024
18 checks passed
@mwcampbell mwcampbell deleted the cargo-deny branch October 13, 2024 12:21
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.

2 participants