Skip to content

Enable strict provenance lints on nightly#1918

Open
carlosmn wants to merge 2 commits into
gtk-rs:mainfrom
carlosmn:cmn/nightly-sa-lints
Open

Enable strict provenance lints on nightly#1918
carlosmn wants to merge 2 commits into
gtk-rs:mainfrom
carlosmn:cmn/nightly-sa-lints

Conversation

@carlosmn

@carlosmn carlosmn commented Mar 5, 2026

Copy link
Copy Markdown
Contributor

Following up from #1917 (and in service to #659) here we add the feature strict-provenance that enables these lints. You can only enable them behind a nightly flag so we also have to put it behind a flag.

A bunch of these tests already enable all flags on nightly so we're covered there but those are for specific subprojects, so I've also added it to the general cargo build that runs on nightly.

@carlosmn carlosmn force-pushed the cmn/nightly-sa-lints branch from 9103ce9 to cb953a9 Compare March 5, 2026 08:42
carlosmn added 2 commits March 5, 2026 09:49
These are only allowed on nightly so we can't just enable them.
Most of the tests run with `--all-features` so the feature will be on by default
but graphene and pango don't so we add it explicitly.
@carlosmn carlosmn force-pushed the cmn/nightly-sa-lints branch from cb953a9 to ffa6f2c Compare March 5, 2026 08:49
@carlosmn carlosmn marked this pull request as ready for review March 5, 2026 08:55
@sdroege

sdroege commented Mar 14, 2026

Copy link
Copy Markdown
Member

That this needs a feature flag etc is adding quite a bit of noise just for testing purposes. I'm not sure that's a good idea for maintainability

@carlosmn

Copy link
Copy Markdown
Contributor Author

I did end up wondering if it's worth doing all of this. Once the lints become stable presumably you can detect this via clippy for some time.

@sdroege

sdroege commented Mar 21, 2026

Copy link
Copy Markdown
Member

Let's do that then and keep this open here for now as reminder :)

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.

2 participants