run-llama/workflows-py
1
0
Fork 0
mirror of https://github.com/run-llama/workflows-py.git synced 2026-08-24 20:01:34 -04:00
Code Issues 18 Packages Projects Releases 10 Wiki Activity

[PR #286] [MERGED] Automatically bump the uv.lock versions on version update #292

New Issue
Closed
opened 2026-02-16 02:17:09 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 02:17:09 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/run-llama/workflows-py/pull/286
Author: @adrianlyjak
Created: 1/16/2026
Status: ✅ Merged
Merged: 1/16/2026
Merged by: @adrianlyjak

Base: main ← Head: claude/add-uv-sync-version-bump-UEJgc

📝 Commits (1)

  • f59f341 feat: run uv sync after version bumping in changeset-version command

📊 Changes

2 files changed (+17 additions, -5 deletions)

View changed files

📝 packages/workflows-dev/src/workflows_dev/changesets.py (+4 -2)
📝 packages/workflows-dev/src/workflows_dev/cli.py (+13 -3)

📄 Description

Modified sync_package_version_with_pyproject to return a boolean indicating whether the pyproject.toml was changed. After syncing all packages, if any pyproject.toml was updated, run uv sync in the root directory to update the lock file.

Otherwise, the first person to make updates after a version release gets a stray change to the lock file.

Would be good to later also enforce frozen lockfiles in ci checks to avoid lock drift

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/run-llama/workflows-py/pull/286 **Author:** [@adrianlyjak](https://github.com/adrianlyjak) **Created:** 1/16/2026 **Status:** ✅ Merged **Merged:** 1/16/2026 **Merged by:** [@adrianlyjak](https://github.com/adrianlyjak) **Base:** `main` ← **Head:** `claude/add-uv-sync-version-bump-UEJgc` --- ### 📝 Commits (1) - [`f59f341`](https://github.com/run-llama/workflows-py/commit/f59f341cfd8d7174f91d109f5254a852a7e5cf87) feat: run uv sync after version bumping in changeset-version command ### 📊 Changes **2 files changed** (+17 additions, -5 deletions) <details> <summary>View changed files</summary> 📝 `packages/workflows-dev/src/workflows_dev/changesets.py` (+4 -2) 📝 `packages/workflows-dev/src/workflows_dev/cli.py` (+13 -3) </details> ### 📄 Description Modified sync_package_version_with_pyproject to return a boolean indicating whether the pyproject.toml was changed. After syncing all packages, if any pyproject.toml was updated, run uv sync in the root directory to update the lock file. Otherwise, the first person to make updates after a version release gets a stray change to the lock file. Would be good to later also enforce frozen lockfiles in ci checks to avoid lock drift --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-16 02:17:09 -05:00
yindo closed this issue 2026-02-16 02:17:09 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
enhancement
good first issue
pull-request
Mirrored from GitHub Pull Request
 question
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: run-llama/workflows-py#292
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?