Repository navigation
chore(deps): let Dependabot update uv.lock by using the uv ecosystem - #159
Merged
Merged
Conversation
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
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.
Why
Dependabot's
pipecosystem changespyproject.tomlbut notuv.lock. The Tests workflow runsuv sync --locked, so every Python dependency PR failed at Install dependencies (#150–#154 each needed a manualuv lockcommit).Change
package-ecosystem: "pip"→"uv"(supported by Dependabot, updatesuv.lockalong with the manifest). Directory, schedule, PR limit, labels, the PyGObject>=3.51ignore, and the github-actionscodeql-actiongroup are unchanged.Note: when a new version still satisfies the
>=floor, the uv updater bumps onlyuv.lockand leaves the floor alone.