Skip to content

cargo: extract lints from declared manifests only - #4274

Open
jrandolf wants to merge 1 commit into
bazelbuild:mainfrom
jrandolf:codex/upstream-cargo-lints
Open

jrandolf wants to merge 1 commit into
bazelbuild:mainfrom
jrandolf:codex/upstream-cargo-lints

Conversation

@jrandolf

@jrandolf jrandolf commented Sep 24, 2026 •

Copy link
Copy Markdown
Contributor

Cargo lint extraction only needs the declared package and optional workspace manifests. Fully resolving the Cargo package also reads workspace members and resources that are absent from a sandboxed Bazel action. Read the manifests directly and preserve workspace lint inheritance.

The regression covers an undeclared workspace member and resource path. The Python test lives in the test package, so downstream users do not need rules_python. A nested downstream consumer check is documented as a manual test.

Validation: both owning tests pass locally on macOS arm64 with Bazel 9.2.0 at 18b85ec: //cargo/private/cargo_toml_info:unit_test and //cargo/tests/cargo_toml_info:declared_manifests_test.

Closes #4290.

@jrandolf
jrandolf force-pushed the codex/upstream-cargo-lints branch from 24715f6 to 18b85ec Compare September 28, 2026 19:15

This branch has not been deployed

No deployments
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.

Cargo lint extraction reads workspace files that are not declared action inputs

1 participant