litestar-org / litestar-org/project-template

build: pin uv resolver with exclude-newer

Open
#19 0 comments 0 reactions 1 assignee View on GitHub

@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:

  1. Pin a static date and bump it manually / on release.
  2. Add a scheduled workflow that rewrites the date to today - 7d and opens a PR (true rolling week).
  3. Rely on the UV_EXCLUDE_NEWER env var in CI only, leaving local dev unpinned.

Proposed tasks

  • Decide static vs. automated rolling cutoff
  • Add [tool.uv] exclude-newer to pyproject.toml
  • (If rolling) add a scheduled workflow to bump the date
  • Document the policy in CONTRIBUTING

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.