Pin Python dependencies to exact versions#350
Merged
JanPetterMG merged 1 commit intomainfrom Feb 11, 2026
Merged
Conversation
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.
This PR replaces compatible release specifiers
~=with exact version pins==for selected Python dependencies.While loosening constraints was intended to allow safe patch updates, it introduces non-deterministic builds and can result in unexpected upstream changes being pulled into CI without explicit review. For infrastructure-related tooling and rendering libraries, even minor updates can introduce behavioral or output differences.
Key changes
~=specifiers with==in requirementsImpact
No functional changes are introduced beyond dependency resolution behavior.