chore: run uv lock after adding exclude-newer duration - #372
Merged
Conversation
tonyandrewmeyer
approved these changes
Jul 8, 2026
tonyandrewmeyer
left a comment
tonyandrewmeyer
left a comment
Collaborator
There was a problem hiding this comment.
Sorry, I missed locking on some of the PRs that added exclude-newer. Thanks for fixing this!
james-garner-canonical
added a commit
that referenced
this pull request
Jul 30, 2026
This PR prepares Jubilant for release. Release notes: ``` v1.12.0: Improved Jubilant logging ``` ``` This feature release improves Jubilant's logging, lowering the default verbosity and presenting app/unit status changes in an easier to read format. Read more: [Configure Jubilant logs](https://canonical.com/juju/docs/ops/latest/howto/write-integration-tests-for-a-charm/#configure-jubilant-logs). ## What's Changed * feat: improve Jubilant logging mechanism in #351 * feat: bump minimum python version to 3.10 in #370 * chore: rolling uv exclude-newer supply-chain quarantine in #368 * chore: set dependabot commit-message prefix to "chore" (no scope) in #367 * chore: add Code of Conduct linking to Ubuntu CoC in #356 * chore: run uv lock after adding exclude-newer duration in #372 * ci: adopt new dependabot conventions in #365 * ci: hash-pin actions and drop zizmor config in #366 * ci: correct hash-pin version comment for upload-sarif action in #376 * ci: pin action version comments to exact tags in #378 **Full Changelog**: v1.11.0...v1.12.0 ```
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
2 participants
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.
I'm sorry for the noise.
In #370, I ran
uv lockbefore pulling in the changes from #368. I didn't expectto write into
uv.lock, the next time you runuvcommands (in Jubilant, it happened when I ranmake lint):The
exclude-newer = "0001-01-01T00:00:00Z"behavior is mentioned here - astral-sh/uv#19022.This PR adds that part in, or else it would update
uv.lockeverytime. The changes touv.locklooks good to me, and I verified thatexclude-newerstill works as expected (I trieduv add uv==0.11.28).