-
Notifications
You must be signed in to change notification settings - Fork 8
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
Cargo Deny #140
Cargo Deny #140
Conversation
The |
Oh right, probably it's missing the |
Try now! EDIT: Now also created new versions for all crates. |
It's the |
It is green, I think that is good. Thanks for all the effort upstream. Feel free to merge :D (Edit: If I don't accidentally close it) Edit: Okay, I accidentally closed and reopened it and somehow CI is a lot less green this time. |
Lol haha why would re-opening the PR matter, other than re-running the checks perhaps... maybe something else got merged in the meantime? Anyway ~ good to go? |
Okay, I did some investigation, and I'm pretty sure that it is because GitHub's The last run we had on
Yep, should be good 🤞 Edit: This problem has been fixed in #163. After merging, this CI should be green again. |
OK, I've merged #163. And I'm getting about a million merge conflicts in every Cargo.toml in the universe now 🫠 |
No worries, I will resolve them. |
This includes a non exclusive list of license we allow in this project due to license compatibility.
Add missing information to Cargo.toml and some small tweaks to keep information and its structure consistent
Also moved them to workspace packages so this is less of a pain next time
Awwww, I can do that one |
All checks are green, let's goooo |
Yet it broke after the merge with enum-debug problems 😢. I think because enum-debug is now still version 1.0.0 in the policy reasoner, which is not compatible with 1.1.0 that we have in Brane. I think this is because we are using tags for versions, and I don't think Cargo will interpret tags as semver as that is not necessarily true. |
This introduces Cargo deny into our CI. With Cargo deny we can check if all dependencies have compatible licenses.
A couple of things still need to be done:
cargo update
to reflect the missing license information I added in these PRs.After that is done the CI check should become green again