Context

Now that we are using uv, there is benefit in keeping the lock file checked in to the repo: it makes our builds faster and more repeatable. However, we also want to make sure we're testing against the latest releases of our dependencies. We can accomplish this by having a PR run once a month that updates the lock file and makes a PR with the changes. This will better help us identify when an upstream change breaks our build. We can reuse some of the logic we have to create backport PRs to create this workflow.

Definition of done

Create the workflow and test it by running it with manual dispatch to see the lock update. This will have to be done on a fork by making the PR branch the default branch and running the workflow.

Pitfalls

N/A