Skip to content

Conversation

@maxisbey
Copy link
Contributor

Summary

Adds a scheduled GitHub Action that updates uv.lock with the latest dependency versions weekly.

Motivation and Context

After removing the highest resolution strategy from the test matrix (which was causing CI failures due to missing platform wheels), we still want to periodically test against the latest versions of our dependencies.

This workflow:

  1. Runs every Monday at 8:00 UTC (and can be triggered manually)
  2. Executes uv lock --upgrade to update all dependencies to their latest compatible versions
  3. Creates a PR with the changes, so CI runs before merging
  4. Only touches uv.lock - does not modify pyproject.toml

How It Works

Uses peter-evans/create-pull-request to automatically create a PR with the updated lockfile. The PR body includes the output from uv lock --upgrade showing what changed.

Repository Setup Required

For this workflow to create PRs, you need to enable "Allow GitHub Actions to create and approve pull requests" in:
Settings → Actions → General → Workflow permissions

Breaking Changes

None.

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines

Adds a scheduled GitHub Action that runs every Monday at 8:00 UTC to
update uv.lock with the latest dependency versions using 'uv lock --upgrade'.

The workflow creates a PR with the changes, allowing CI to run before
merging. This ensures we periodically test against the latest versions
of our dependencies without the instability of testing 'highest' on
every PR.

Claude-Generated-By: Claude Code (cli/claude-opus-4-5=100%)
Claude-Steers: 3
Claude-Permission-Prompts: 4
Claude-Escapes: 0
@maxisbey maxisbey merged commit fc5cb6a into main Jan 16, 2026
25 checks passed
@maxisbey maxisbey deleted the ci-weekly-lockfile-update branch January 16, 2026 08:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants