Skip to content

build: refresh uv.lock self-version to 0.2.1 - #32

Merged
CameronBrooks11 merged 1 commit into
mainfrom
build/refresh-uv-lock
Aug 20, 2026
Merged

build: refresh uv.lock self-version to 0.2.1#32
CameronBrooks11 merged 1 commit into
mainfrom
build/refresh-uv-lock

Conversation

@CameronBrooks11

Copy link
Copy Markdown
Member

The committed uv.lock pinned the editable marlin-host package at version = "0.1.0", while pyproject.toml and marlin_host/__init__.py are both at
0.2.1. Every uv run / uv lock regenerated that one line, dirtying the
working tree on each local run.

Regenerate the lock so its self-version matches the package. One-line change;
uv lock --check now passes clean. No dependency changes.

https://claude.ai/code/session_017N6LZRKsJYXcNMQZqeEvpd

The committed lock pinned the editable marlin-host at 0.1.0 while
pyproject and __init__ are at 0.2.1, so every `uv run`/`uv lock`
rewrote the line — harmless churn, but it dirtied the tree on each
local run. Regenerate the lock so it matches the package version.

Claude-Session: https://claude.ai/code/session_017N6LZRKsJYXcNMQZqeEvpd
@CameronBrooks11
CameronBrooks11 merged commit faf8aa5 into main Aug 20, 2026
5 checks passed
@CameronBrooks11
CameronBrooks11 deleted the build/refresh-uv-lock branch August 20, 2026 20:57
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.

1 participant