ci: use Cargo build warnings setting#6207
Closed
coyaSONG wants to merge 1 commit into
Closed
Conversation
Member
|
This automated contribution does not meet our upcoming ai policy #6141 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
RUSTFLAGSandRUSTDOCFLAGSwarning overrides with Cargo'sCARGO_BUILD_WARNINGS: denysettingWhy
Closes #6205.
Cargo now provides
build.warningsspecifically for configuring the effective warning level of local packages. Using its environment-variable form removes the need to maintain separate low-level compiler and rustdoc flags.Impact
This is a CI-only configuration change. It does not affect PyO3's runtime behavior, dependencies, or public API.
Validation
.github/workflows/build.ymlsuccessfully with Ruby's YAML parsergit diff --checkbuild.warningsconfiguration documentationThe full nox suite was not run because the change only updates the reusable GitHub Actions workflow environment.
Authorship disclosure
This contribution was prepared by OpenAI Codex on behalf of @coyaSONG, after reviewing
Contributing.md, the pull request template, and the Code of Conduct.