chore: pin dependency upper bounds and install the fleet by tag (#131) - #137
Merged
Conversation
Runtime deps were open-ended floors and fleet installs go through `uv tool install git+…`, which resolves fresh from PyPI and ignores uv.lock, so a breaking upstream major (an mcp 2.0, a fastapi 1.0) would land on every node overnight. Cap each dep below its next major and regenerate uv.lock. bootstrap.sh also tracked the moving `main` HEAD; it now resolves and installs the latest published release tag by default (override with --ref / $OMIND_REF), so two nodes bootstrapped hours apart get the same tested code. Closes #131. Co-Authored-By: Claude Fable 5 <[email protected]>
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.
Closes #131.
Runtime deps were open-ended floors, and fleet installs go through
uv tool install git+…which resolves fresh from PyPI and ignoresuv.lock— so a breaking upstream major (anmcp2.0, afastapi1.0 rewrite) would land on every node at the next self-update overnight.embedextra) below its next major; regenerateuv.lock(resolved versions unchanged — current versions satisfy the caps).scripts/bootstrap.shnow resolves and installs the latest published release tag by default instead of the movingmainHEAD (override with--ref/$OMIND_REF), so nodes bootstrapped hours apart get the same tested code.Test plan
uv lockregenerates cleanly;bash -non the script passes; tag-resolution verified against the live remote.🤖 Generated with Claude Code
Proudly Made in Nebraska. Go Big Red! 🌽 https://xkcd.com/2347/