litestar-org / litestar-org/project-template
build: pin uv resolver with exclude-newer
Open
@hasansezertasan is already working on this.
Since Jul 22, 2026.
dependencies
infra
- Dominant language
- Python
- Stars
- 13
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Context
Now that we're on uv (#18), we can make dependency resolution reproducible by refusing to consider distributions published after a cutoff. See tool.uv.exclude-newer.
⚠️ Open question — this is not a rolling window
exclude-newer takes a fixed RFC 3339 timestamp, not "last 1 week." Options:
- Pin a static date and bump it manually / on release.
- Add a scheduled workflow that rewrites the date to
today - 7dand opens a PR (true rolling week). - Rely on the
UV_EXCLUDE_NEWERenv var in CI only, leaving local dev unpinned.
Proposed tasks
- Decide static vs. automated rolling cutoff
- Add
[tool.uv]exclude-newertopyproject.toml - (If rolling) add a scheduled workflow to bump the date
- Document the policy in CONTRIBUTING
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.