Changes in contributing-coding-guidelines.md

ec76a6b2 - Add documentation for adding new crates (#12300)

Fri, 09 Jan 2026 18:40:35 +0000

Add documentation for adding new crates (#12300)This commit adds contributor documentation to our book about how to adda new crate to the workspace with respect to the crates.io-based trustedpublishing workflow. The error messages in the verify-publish scripthave also been adjusted to point to this URL. List of files: /wasmtime-44.0.1/docs/contributing-coding-guidelines.md

95942cb5 - Add contrib docs about unsafe code (#11177)

Thu, 03 Jul 2025 21:01:45 +0000

Add contrib docs about unsafe code (#11177)This is my attempt to summarize the discussion from the Wasmtime meetingtoday to write down and codify some of the thinking about `unsafe` codeand how we handle it within Wasmtime over time. List of files: /wasmtime-44.0.1/docs/contributing-coding-guidelines.md

4c8edb95 - More clearly flag internal crates as such (#10963)

Fri, 06 Jun 2025 21:13:36 +0000

More clearly flag internal crates as such (#10963)* More clearly flag internal crates as suchThis commit is an attempt to more clearly flag internal crates in thisproject as internal and not intended for external use. Specifically:* Many crates are renamed from `wasmtime-foo` to `wasmtime-internal-foo`.* All of these crates now have `INTERNAL: ...` in their crates.io description.* All of these crates now have a warning at the top of their documentation discouraging use.This change is a result of rustsec/advisory-db#1999 where the goal is tobe crystal clear from a project perspective that usage of these cratesare highly discouraged and not supported. We'll still probably get suchadvisories but we won't be considering them CVEs from the project itselfdue to the internal nature of these crates and the discouragingwarnings.Some concrete changes used here are:* Inter-crate dependencies still use `wasmtime_foo` for naming and do so with Cargo's package-renaming features.* Crate renames are specified at the workspace level so the rename is only in one locations and all other inherit it.* Contribution documentation now has some brief guidelines about crate organization.* Update vet config* Update checks for wasmtime-fiberprtest:full* Update publish script* Another fiber rename* Fix some doc tests List of files: /wasmtime-44.0.1/docs/contributing-coding-guidelines.md

92cfda1b - refactor(docs): more conversions of sh to console for copy-paste (#10707)

Fri, 02 May 2025 14:44:25 +0000

refactor(docs): more conversions of sh to console for copy-paste (#10707)This commit udpates more instructions on various READMEs to avoid `$`for easy copy-pasting, and also use `console` where appropriate.Signed-off-by: Victor Adossi List of files: /wasmtime-44.0.1/docs/contributing-coding-guidelines.md

584f6686 - Clarify MSRV intent in contributor docs (#9936)

Tue, 07 Jan 2025 00:42:52 +0000

Clarify MSRV intent in contributor docs (#9936)Currently we support 3 versions of rustc (current, current-1, andcurrent-2). This is probably too small a window for someone out there onthe internet so this commit adds a clarification with some rationale forthe current policy as well as an olive branch for "please talk to us ifyou want a wider window". Basically I wanted to update this toexplicitly declare intent that we're open to reconsidering this policyas necessary (without actually committing to any alternative policyyet). List of files: /wasmtime-44.0.1/docs/contributing-coding-guidelines.md

c0c3e798 - Add contributors docs about lints/warnings/clippy (#9323)

Sat, 28 Sep 2024 21:15:30 +0000

Add contributors docs about lints/warnings/clippy (#9323)Inspired by #9318 I realized we haven't actually documented anythingabout compiler warnings or Clippy warnings in our contributor docs, so Ihave aspired to do so in this commit. My goal is to reflect the currentstate of the repository in this documentation, not add anything new. List of files: /wasmtime-44.0.1/docs/contributing-coding-guidelines.md

f900a884 - Don't gate on `cargo vet` for PRs (#8343)

Thu, 11 Apr 2024 23:06:03 +0000

Don't gate on `cargo vet` for PRs (#8343)* Don't gate on `cargo vet` for PRsGate the `cargo vet` step for the merge queue by default but for PRsdon't fail the PR's CI and instead allow entering the queue with afailing `cargo vet` entry. This should help make it easier to land a`cargo vet` entry on `main` outside of a PR while not requiring the PRis rebased.* Fix syntax* Trigger cargo vet failures* Fix conditional* Try to fix conditional* More changes* Revert "Trigger cargo vet failures"This reverts commit 14ba8cb52c955a6843c8c80c19d1274dfc8bb97e.* Update Cargo.lock but also have vet pass* Try different syntax* Revert "Update Cargo.lock but also have vet pass"This reverts commit 16798388481f9ad57292bedb9b5643a6dcb87297.* Remove debugging* Spruce up some comments* Update docs List of files: /wasmtime-44.0.1/docs/contributing-coding-guidelines.md

a6a51b71 - Update Wasmtime's policy on `cargo vet` (#8259)

Fri, 29 Mar 2024 16:42:40 +0000

Update Wasmtime's policy on `cargo vet` (#8259)* Update Wasmtime's policy on `cargo vet`This was discussed at today's Wasmtime meeting out of some concernsaround our current policies. Namely I felt the current state of affairsis not striking the right balance between cost and benefit with ourusage of `cargo vet`. After discussion we've reached consensus aroundtwo changes to our `cargo vet` policy documented here in this PR:* An exemption can be added for "popular crates" at any time with no review required. This should handle most big crates that are needed for various dependencies. The thinking behind this is that a supply-chain attack against these crates is highly likely to be detected in a short time due to their popularity. Coupled with the fact that changes to Wasmtime take a minimum of two weeks to get released means that it's an unlikely exploitation vector.* Maintainers are recommended to push directly to contributor's PRs for `cargo vet` entries instead of making separate PRs. This avoids the need for contributor rebasing and additionally solves the problem where the `vet` entries land in a separate PR but then the contributor's PR takes much longer to land. In the interim some `vet` entries have been cleaned up by accident which requires re-landing the PR to add the entries.* Review comments List of files: /wasmtime-44.0.1/docs/contributing-coding-guidelines.md

5c8bce70 - Document `cargo vet` in contributing docs (#7635)

Tue, 05 Dec 2023 17:21:36 +0000

Document `cargo vet` in contributing docs (#7635)I realized just now that we haven't actually documented our usage of`cargo vet` anywhere in our contributing documentation (or not that Icould find), so I decided to try and rectify that! List of files: /wasmtime-44.0.1/docs/contributing-coding-guidelines.md

a04c4930 - Update Rust in CI to 1.72.0, clarify Wasmtime's MSRV (#6900)

Thu, 31 Aug 2023 20:04:59 +0000

Update Rust in CI to 1.72.0, clarify Wasmtime's MSRV (#6900)* Update Rust in CI to 1.72.0* Update CI, tooling, and docs for MSRVThis commit codifies an MSRV policy for Wasmtime at "stable minus two"meaning that the latest three releases of Rust will be supported. Thisis enforced on CI with a full test suite job running on Linux x86_64with the minimum supported Rust version. The full test suite will usethe latest stable version. A downside of this approach is that newchanges may break MSRV support on non-Linux or non-x86_64 platforms andwe won't know about it, but that's deemed a minor enough risk at thistime.A minor fix is applied to Wasmtime's `Cargo.toml` to support Rust 1.70.0instead of requiring Rust 1.71.0* Fix installation of rust* Scrape MSRV from Cargo.toml* Cranelift is the same as Wasmtime's MSRV now, more words too* Fix a typo List of files: /wasmtime-44.0.1/docs/contributing-coding-guidelines.md

47d3c8de - docs: Better title formatting for the coding guidelines

Fri, 07 Aug 2020 23:49:58 +0000

docs: Better title formatting for the coding guidelines List of files: /wasmtime-44.0.1/docs/contributing-coding-guidelines.md

986f9f79 - Merge the CONTRIBUTING.md files

Tue, 25 Feb 2020 19:48:03 +0000

Merge the CONTRIBUTING.md files List of files: /wasmtime-44.0.1/docs/contributing-coding-guidelines.md