chore(deps): dependabot moves the lock, a person moves a floor - #17
Merged
Merged
Conversation
PR #11 was uv.lock and nothing else. PR #15 also rewrote pyproject.toml, raising four published floors that nothing asked it to raise: openai from >=1.50 to >=3.11.0 across ten lines, narrowing the openai extra, all eight vendor extras and `all` at once, plus mcp, mujoco and onnxruntime. None of those floors had ever been tested. The lock has resolved openai 3.x since the first commit, mcp 2.1.1 throughout, onnxruntime 1.27.0. They are hand-written claims about what a consumer may install against, and they carry comments explaining themselves. A weekly bot should not be editing them. versioning-strategy: lockfile-only is supported on the uv ecosystem (dependabot-core#12162) though the options reference still omits it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Unblocks #15, and stops the same thing happening every week.
What changed
One key on the
uvecosystem entry:Why
PR #11 was
uv.lockand nothing else. #15 also rewrotepyproject.toml, raising four published floors that nothing asked it to raise:mcp>=2.0,<3>=2.2.0,<3openai>=1.50>=3.11.0allmujoco>=3.12,<4>=3.13.0,<4onnxruntime>=1.20>=1.29.0Those floors are hand-written claims about what a consumer may install against, and several of them carry comments explaining themselves. They are not the lock, and a weekly bot should not be editing them.
None of them had ever been tested, either. The lock has resolved
openai3.x since the first commit (3.5.0, 2026-08-28),mcp2.1.1 throughout,onnxruntime1.27.0. Nothing in CI has ever exercised the lower bound it claims.What this does not fix
openai>=1.50is still wrong, in the other direction:quackd/agent/providers/openai.pycallsself.client.responses.create(...), and the Responses API did not exist in openai-python 1.50. That is a floor a person should correct deliberately, with a reason, which is exactly what this change makes room for.Note
versioning-strategyis supported on theuvecosystem (dependabot/dependabot-core#12162) though the options reference still omits it. The config parses as valid YAML and the key lands where GitHub expects it.After this merges
@dependabot rebaseon #15 regenerates it against currentmainas a lock-only change, which resolves its conflict too -- that conflict is inuv.lockalone,pyproject.tomlalready auto-merges.🤖 Generated with Claude Code