fix: pin versions - #302
Merged
Merged
Conversation
Add explicit upper bounds to unbounded >= dependencies to prevent unintended major-version upgrades. Keep ~= specifiers where already present. Bump protobuf floor to >=5.0.0, fix anyio and langgraph dev constraints to resolve uv sync conflicts.
ArthurTonial
force-pushed
the
fix/pin-version-0.36.0
branch
from
September 3, 2026 16:57
681d0a6 to
50194df
Compare
cassiofariasmachado
approved these changes
Sep 3, 2026
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
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.
Description
Replaces
~=(compatible release) pin specifiers with explicit>=x,<Nmajor-version ranges for all runtime dependencies inpyproject.toml. This makes upper bounds intentional and documented rather than an implicit side-effect of the~=operator.Also bumps the
protobuflower bound from>=4.25.0to>=5.0.0.Related Issue
N/A
Type of Change
Please check the relevant option:
How to Test
uv syncfrom a clean environment — resolution should succeed with no conflicts.uv run pytestuv.lockfall within the new declared ranges.Checklist
Before submitting your PR, please review and check the following:
Breaking Changes
None.