You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
## Summary
- Add `exclude-newer = "2026-03-25T00:00:00Z"` to `[tool.uv]` — prevents
uv from resolving any Python package published in the last 7 days during
fresh resolves, giving the community time to detect and yank malicious
releases (motivated by recent Axios npm and litellm supply chain
attacks).
- Pin `jlumbroso/free-disk-space` from mutable `@main` to `@v1.3.1`
across all CI workflows.
- Pin `docker-practice/actions-setup-docker` from mutable `@master` to
`@v1`.
- Pin `pip install uv` in `.readthedocs.yaml` to `uv==0.9.2`.
## Context
Recent supply chain attacks (Axios npm hijack, litellm poisoned scanner)
highlighted gaps in our dependency resolution and CI action pinning.
This PR addresses the lowest-hanging fruit. Follow-up PRs planned for:
- SBOM generation via `syft` in the release pipeline
- CodeQL / SAST scanning workflow
## Test plan
- [ ] CI workflows pass with pinned action versions
- [ ] `uv lock` still works with `exclude-newer` set (only affects fresh
resolves, not existing lockfile)
- [ ] ReadTheDocs builds succeed with pinned uv version
🤖 Generated with [Claude Code](https://claude.com/claude-code)
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
0 commit comments