Repository navigation
docs: route uv-compiled requirements to Dependabot uv - #29
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configurationConfiguration used: Organization UI Review profile: QUIET Plan: Advanced Run ID: 📒 Files selected for processing (1)
Comment |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f64abc8b4b
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| per package ecosystem and lockfile directory. Requirements files compiled with | ||
| `uv pip compile` use the `uv` ecosystem and keep uv's generated header, which | ||
| Dependabot reads for the compile options; the `pip` ecosystem regenerates them | ||
| with pip-tools and loses universal resolution. Version updates run weekly and |
There was a problem hiding this comment.
For repositories with uv-compiled requirements, the adoption flow in docs/adopting.md only tells maintainers to copy templates/dependabot.yml and retain the applicable entries, but that template contains entries only for GitHub Actions, npm, Cargo, and rust-toolchain. Following the documented flow therefore provides no uv entry and leaves these requirements without version updates unless the adopter independently knows how to author one; add a uv stanza to the template or explicitly instruct adopters to create it.
AGENTS.md reference: AGENTS.md:L7-L9
Useful? React with 👍 / 👎.
Change
hardware and camera compile hash-pinned requirements with
uv pip compile --universal. Dependabot'spipecosystem regenerates those files with pip-tools, which has no universal mode and would break Python-version-dependent pins; itsuvecosystem reads the compile options from uv's generated header. The dependency standard now says to useuvfor those files and keep the header (hardware#58 and camera#5 do this).Validation
just checkpasses. The first real Dependabotuvupdate in hardware or camera is the runtime proof; none has run yet.