Pin dependencies more tightly, updating versions#1558
Open
rolandwalker wants to merge 1 commit intomainfrom
Open
Pin dependencies more tightly, updating versions#1558rolandwalker wants to merge 1 commit intomainfrom
rolandwalker wants to merge 1 commit intomainfrom
Conversation
Some dependencies had no versioning; others used ">=" which is prone to breakage as libraries have breaking changes. This way means more maintenance but is safer against breakage. Some projects also check in the lockfile for perfect reproducibility. Where a ">=" was used, the version was generally updated to the latest, which is probably what was being used in practice. The "~=" operator allows the patch version to increment.
scottnemes
approved these changes
Feb 15, 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
2 participants
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
Some dependencies had no versioning; others used
>=which is prone to breakage as libraries have breaking changes.This way means more maintenance but is safer against breakage.
Some projects also check in the lockfile for perfect reproducibility.
Where a
>=was used, the version was generally updated to the latest, which is probably what was being used in practice.The
~=operator allows the patch version to increment.Checklist
changelog.mdfile.AUTHORSfile (or it's already there).