[PR #136] [MERGED] [release] Carry uv.lock in the release commit #140

New issue

Closed

opened 2026-10-13 19:47:53 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-13 19:47:53 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/Glitchy-Sheep/boosty-downloader/pull/136
Author: @Glitchy-Sheep
Created: 8/9/2026
Status: ✅ Merged
Merged: 8/9/2026
Merged by: @Glitchy-Sheep

Base: main ← Head: fix/release-bumps-lock

📝 Commits (1)

a1a882f fix: 🐛 The release commit now carries uv.lock alongside pyproject.toml

📊 Changes

2 files changed (+8 additions, -4 deletions)

View changed files

📝 scripts/release.py (+7 -3)
📝 uv.lock (+1 -1)

📄 Description

Summary

The v3.2.0 tag preflight refused to run: the release commit had bumped pyproject.toml but not uv.lock, and uv.lock records the project's own version. The first uv run after the merge silently refreshed the stale lock, and the wizard's clean-tree check tripped over its own runner's side effect.

Fix

The wizard runs uv lock right after the version bump and includes uv.lock in the release commit
The preview ladder shows the new git add - preview and execution share one source, so they cannot drift
The refreshed lock for 3.2.0 rides in this PR: after the merge the pending task release:tag passes

Notes

Born from the uv migration: poetry.lock never recorded the project's own version, so the old flow could not hit this

_{🔄 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/Glitchy-Sheep/boosty-downloader/pull/136 **Author:** [@Glitchy-Sheep](https://github.com/Glitchy-Sheep) **Created:** 8/9/2026 **Status:** ✅ Merged **Merged:** 8/9/2026 **Merged by:** [@Glitchy-Sheep](https://github.com/Glitchy-Sheep) **Base:** `main` ← **Head:** `fix/release-bumps-lock` --- ### 📝 Commits (1) - [`a1a882f`](https://github.com/Glitchy-Sheep/boosty-downloader/commit/a1a882fd0c8328dcf016a119854eaeec0ed9a526) fix: :bug: The release commit now carries uv.lock alongside pyproject.toml ### 📊 Changes **2 files changed** (+8 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `scripts/release.py` (+7 -3) 📝 `uv.lock` (+1 -1) </details> ### 📄 Description ## Summary The v3.2.0 tag preflight refused to run: the release commit had bumped `pyproject.toml` but not `uv.lock`, and `uv.lock` records the project's own version. The first `uv run` after the merge silently refreshed the stale lock, and the wizard's clean-tree check tripped over its own runner's side effect. ## Fix - The wizard runs `uv lock` right after the version bump and includes `uv.lock` in the release commit - The preview ladder shows the new `git add` - preview and execution share one source, so they cannot drift - The refreshed lock for 3.2.0 rides in this PR: after the merge the pending `task release:tag` passes ## Notes - Born from the uv migration: `poetry.lock` never recorded the project's own version, so the old flow could not hit this --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-13 19:47:53 +00:00