docs: Declare build-rs as intentional

rust-lang · weihanglo · Nov 13, 2024 · Mar 14, 2022 · Mar 14, 2022 · Mar 14, 2022
commit 9814045a034dd361bf590fbcaba7b54b44c8ff14
diff --git a/crates/build-rs/README.md b/crates/build-rs/README.md
@@ -0,0 +1,2 @@
+> This crate is maintained by the Cargo team for use by the wider
+> ecosystem. This crate follows semver compatibility for its APIs.
diff --git a/crates/build-rs/src/lib.rs b/crates/build-rs/src/lib.rs
@@ -1,6 +1,9 @@
 //! build-rs provides a strongly typed interface around the Cargo build script
 //! protocol. Cargo provides inputs to the build script by environment variable
 //! and accepts commands by printing to stdout.
+//!
+//! > This crate is maintained by the Cargo team for use by the wider
+//! > ecosystem. This crate follows semver compatibility for its APIs.
 #![cfg_attr(all(doc, feature = "unstable"), feature(doc_auto_cfg, doc_cfg))]
 #![allow(clippy::disallowed_methods)] // HACK: deferred resoling this
 #![allow(clippy::print_stdout)] // HACK: deferred resoling this

diff --git a/src/doc/contrib/src/team.md b/src/doc/contrib/src/team.md
@@ -170,6 +170,7 @@ The degree of process is correlated with the degree of change being proposed:
 
 Per the [Rust crate ownership policy](https://forge.rust-lang.org/policies/crate-ownership.html), the Cargo team's "Intentional Artifacts" include:
 
+- [build-rs](https://crates.io/crates/build-rs)
 - [cargo-credential](https://crates.io/crates/cargo-credential)
 - [cargo-platform](https://crates.io/crates/cargo-platform)
 - [cargo-util-schemas](https://crates.io/crates/cargo-util-schemas)
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1,2 @@
		> This crate is maintained by the Cargo team for use by the wider
		> ecosystem. This crate follows semver compatibility for its APIs.
Copy link Contributor CAD97 Nov 8, 2024 Choose a reason for hiding this comment The reason will be displayed to describe this comment to others. Learn more. We probably want to explicitly exempt the `unstable` feature here, and/or migrate it to using a cfg (like `procmacro2_semver_exempt`) instead. Copy link Contributor Author epage Nov 9, 2024 Choose a reason for hiding this comment The reason will be displayed to describe this comment to others. Learn more. My assumption is that its fine as that feature is documented as unstable. I'm not even sure why that line is encouraged in the policy. Pretty much every lib is assumed to follow semver.