Update uv.lock#1107
Merged
rickecon merged 6 commits intoPSLmodels:masterfrom Apr 16, 2026
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #1107 +/- ##
=======================================
Coverage 72.85% 72.85%
=======================================
Files 21 21
Lines 5201 5201
=======================================
Hits 3789 3789
Misses 1412 1412
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
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.
This PR:
'**.lock'to the paths inbuild_and_test.ymlso that any changes to theuv.lockfile trigger the GH Action CI tests inbuild_and_test.ymluv.lockfile would only test therufflinter (see PR Bump pillow from 12.1.1 to 12.2.0 #1102, PR Bump pytest from 9.0.2 to 9.0.3 #1103, PR Bump pygments from 2.19.2 to 2.20.0 #1105, PR Bump requests from 2.32.5 to 2.33.0 #1106). This changes the behavior so that any change to theuv.lockfile triggers the full set of GH Action CI tests inbuild_and_test.yml.uv.lockfile to correspond with the currentogcorepackage version of this PR. I noticed that theuv.lockfile in the previous PRs was using the previous version ofogcore. The workflow with any future PRs that change the version should be:ogcorepackage version inpyproject.tomlandogcore/__init__.pyand associated descriptions in theCHANGELOG.mdfile.uv lockin the terminal. This will create a new version of theuv.lockthat is derived from thepyproject.tomlfile that has the new version number.uv.lockfile.cc: @jdebacker