Stream: git-wasmtime

Topic: wasmtime / PR #8017 Run `cargo vet regenerate audit-as-cr...


view this post on Zulip Wasmtime GitHub notifications bot (Feb 28 2024 at 18:34):

elliottt requested abrown for a review on PR #8017.

view this post on Zulip Wasmtime GitHub notifications bot (Feb 28 2024 at 18:34):

elliottt requested wasmtime-default-reviewers for a review on PR #8017.

view this post on Zulip Wasmtime GitHub notifications bot (Feb 28 2024 at 18:34):

elliottt opened PR #8017 from elliottt:trevor/audit-as-crates-io to bytecodealliance:main:

To unblock the release process, run cargo vet regenerate audit-as-crates-io to
include entries for both wasmtime-c-api and wasmtime-c-api-macros.
<!--
Please make sure you include the following information:

Our development process is documented in the Wasmtime book:
https://docs.wasmtime.dev/contributing-development-process.html

Please ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->

view this post on Zulip Wasmtime GitHub notifications bot (Feb 28 2024 at 18:35):

elliottt requested alexcrichton for a review on PR #8017.

view this post on Zulip Wasmtime GitHub notifications bot (Feb 28 2024 at 18:44):

pchickey submitted PR review.

view this post on Zulip Wasmtime GitHub notifications bot (Feb 28 2024 at 18:44):

elliottt updated PR #8017.

view this post on Zulip Wasmtime GitHub notifications bot (Feb 28 2024 at 18:45):

elliottt edited PR #8017:

To unblock the release process, run cargo vet regenerate audit-as-crates-io to include entries for both wasmtime-c-api and wasmtime-c-api-macros.

Additionally, I ran:

$ cargo vet trust wasmtime-c-api-macros
$ cargo vet trust wasmtime-c-api-impl

Which seems to match the existing entries for things published by wasmtime-publish.
<!--
Please make sure you include the following information:

Our development process is documented in the Wasmtime book:
https://docs.wasmtime.dev/contributing-development-process.html

Please ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->

view this post on Zulip Wasmtime GitHub notifications bot (Feb 28 2024 at 18:49):

elliottt updated PR #8017.

view this post on Zulip Wasmtime GitHub notifications bot (Feb 28 2024 at 18:52):

elliottt updated PR #8017.

view this post on Zulip Wasmtime GitHub notifications bot (Feb 28 2024 at 18:52):

elliottt edited PR #8017:

To unblock the release process, run cargo vet regenerate audit-as-crates-io to include entries for both wasmtime-c-api and wasmtime-c-api-macros.

Additionally, I certified wasmtime-c-api-macros and wasmtime-c-api-impl with wildcard audits, and the usual message about them being BA projects.

Which seems to match the existing entries for things published by wasmtime-publish.
<!--
Please make sure you include the following information:

Our development process is documented in the Wasmtime book:
https://docs.wasmtime.dev/contributing-development-process.html

Please ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->

view this post on Zulip Wasmtime GitHub notifications bot (Feb 28 2024 at 18:52):

elliottt edited PR #8017:

To unblock the release process, run cargo vet regenerate audit-as-crates-io to include entries for both wasmtime-c-api and wasmtime-c-api-macros.

Additionally, I certified wasmtime-c-api-macros and wasmtime-c-api-impl with wildcard audits, and the usual message about them being BA projects.

<!--
Please make sure you include the following information:

Our development process is documented in the Wasmtime book:
https://docs.wasmtime.dev/contributing-development-process.html

Please ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->

view this post on Zulip Wasmtime GitHub notifications bot (Feb 28 2024 at 18:53):

elliottt updated PR #8017.

view this post on Zulip Wasmtime GitHub notifications bot (Feb 28 2024 at 19:09):

elliottt edited PR #8017:

To unblock the release process, run cargo vet regenerate audit-as-crates-io to include entries for both wasmtime-c-api and wasmtime-c-api-macros.

Additionally, I certified wasmtime-c-api-macros and wasmtime-c-api-impl with wildcard audits, and the usual message about them being BA projects.

Commands run:

$ cargo vet regenerate audit-as-crates-io
$ cargo vet certify wasmtime-c-api-macros --wildcard wasmtime-publish --who "Trevor Elliott <telliott@fastly.com>"
$ cargo vet certify wasmtime-c-api-impl --wildcard wasmtime-publish --who "Trevor Elliott <telliott@fastly.com>"

<!--
Please make sure you include the following information:

Our development process is documented in the Wasmtime book:
https://docs.wasmtime.dev/contributing-development-process.html

Please ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->

view this post on Zulip Wasmtime GitHub notifications bot (Feb 28 2024 at 19:37):

elliottt merged PR #8017.


Last updated: Dec 23 2024 at 12:05 UTC