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

vet: trust the windows crates #7846

Merged
merged 1 commit into from
Jan 30, 2024

Conversation

abrown
Copy link
Contributor

@abrown abrown commented Jan 30, 2024

Like the rest of the windows-* crates published by Kenny Kerr, this change also adds the windows crate itself to the trusted list. This is necessary for use in #7807.

Like the rest of the `windows-*` crates published by Kenny Kerr, this
change also adds the `windows` crate itself to the trusted list. This is
necessary for use in bytecodealliance#7807.
@abrown abrown requested a review from a team as a code owner January 30, 2024 00:32
@abrown abrown requested review from fitzgen and removed request for a team January 30, 2024 00:32
@alexcrichton alexcrichton added this pull request to the merge queue Jan 30, 2024
Merged via the queue into bytecodealliance:main with commit 54530ce Jan 30, 2024
19 checks passed
@abrown abrown deleted the vet-windows-crate branch January 30, 2024 17:15
abrown added a commit to abrown/wasmtime that referenced this pull request Feb 8, 2024
In bytecodealliance#7846 I added `cargo-vet` entries to trust the `windows` crate, just
like we already trust several related `windows-*` crates. I did not,
however, update the lockfile, which means that bytecodealliance#7807 continued to fail
the `cargo vet --locked` CI check. This change is the result of simply
running `cargo vet`.
github-merge-queue bot pushed a commit that referenced this pull request Feb 8, 2024
In #7846 I added `cargo-vet` entries to trust the `windows` crate, just
like we already trust several related `windows-*` crates. I did not,
however, update the lockfile, which means that #7807 continued to fail
the `cargo vet --locked` CI check. This change is the result of simply
running `cargo vet`.
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