bump-backend.sh: keep uv.lock version in lockstep#71
Open
jcschaff wants to merge 1 commit into
Open
Conversation
The 0.6.0/0.7.0 bumps updated version.py + pyproject.toml but not uv.lock's own biosim-server version entry, leaving it stale (harmless — package=false means `uv sync --frozen` doesn't enforce the project version — but confusing and it showed up as a stray diff on every `uv` run). bump-backend.sh now also rewrites the biosim-server version in uv.lock (a targeted perl on the package block; no re-resolve needed) and stages it. It replaces whatever version is present, so it self-heals prior drift. Also sync the current uv.lock to 0.7.0 to clear the existing drift. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AzpYYAXPMj1SyxgWf9Lgtm
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The 0.6.0 and 0.7.0 bumps updated
version.py+pyproject.tomlbut notuv.lock's ownbiosim-serverversion entry, leaving it stale. It's harmless at build time (package = falsemeansuv sync --frozendoesn't enforce the project's own version — which is why the 0.6.0/0.7.0 image builds still passed), but it's confusing and reappears as a stray diff on everyuvrun.bump-backend.shnow also rewrites thebiosim-serverversion inuv.lock(a targetedperlon the package block — no re-resolve, so no dependency churn) and stages it alongsideversion.py/pyproject.toml. It replaces whatever version is present, so it self-heals any prior drift on the next bump.uv.lockto 0.7.0 to clear the existing drift now (single-line change, no dep churn).🤖 Generated with Claude Code
https://claude.ai/code/session_01AzpYYAXPMj1SyxgWf9Lgtm