Skip to content

Conversation

@G-Rath
Copy link
Collaborator

@G-Rath G-Rath commented Dec 3, 2025

This helps to ensure our advisories are in a good state

@G-Rath G-Rath force-pushed the run-linter branch 12 times, most recently from 72f483b to 9ee4418 Compare December 3, 2025 21:15
@G-Rath G-Rath changed the title ci: run osv-linter ci: run osv-linter over advisories Dec 3, 2025
@G-Rath
Copy link
Collaborator Author

G-Rath commented Dec 3, 2025

For now I just wanted to get the linter running in CI to showcase the findings and our fixes - I actually don't think it'll be a big deal to not have this landed since the process should be very stable so really the value comes from just these initial fixups, but then again there's probably no reason not to land it 🤷

Either way, I'll get stuff like documentation done later when we're closer to actually maybe landing this

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