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(ci): Validate cargo-deny output in CI and check license compatibility #1016

Merged
merged 3 commits into from
Sep 4, 2024

Conversation

jszwedko
Copy link
Member

@jszwedko jszwedko commented Sep 4, 2024

This PR checks license compatibility using cargo-deny (updating the configuration) and also adds it as a CI check.

@jszwedko jszwedko added the no-changelog Changes in this PR do not need user-facing explanations in the release changelog label Sep 4, 2024
Was using an old version of cargo-deny when I updated this confg

Signed-off-by: Jesse Szwedko <[email protected]>
@jszwedko jszwedko requested a review from pront September 4, 2024 22:56
"Zlib",
]

unlicensed = "warn"
Copy link
Member Author

Choose a reason for hiding this comment

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

These config options default to error now after EmbarkStudios/cargo-deny#611

@@ -1,27 +1,41 @@
[licenses]
allow = [
"MIT",
Copy link
Member Author

@jszwedko jszwedko Sep 4, 2024

Choose a reason for hiding this comment

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

Sorted this list and added 0BSD, BSL-1.0, and Unicode-DFS-2016 based on Vector's deny.toml.

@jszwedko jszwedko added this pull request to the merge queue Sep 4, 2024
Merged via the queue into main with commit 7283fe9 Sep 4, 2024
15 checks passed
@jszwedko jszwedko deleted the jszwedko/check-licenses branch September 4, 2024 23:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-changelog Changes in this PR do not need user-facing explanations in the release changelog
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants