Use compatible versions rather than specific version of dependencies #70
Conversation
This file contains 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
Previously downsteam projects must use these exact versions, now they can use anything compatible with the test helpers versions.
Pezmc
changed the title
knolleary
approved these changes
Sep 19, 2023
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.
While working on #69 I noted that all dependencies for node-red-node-test-helper are declares with specific versions.
This means that downstream projects must use these exact versions of these dependencies. Which becomes a problem when there is a CVE affecting one (semver for example), as an upstream update is required before any downstream project can use a version with a fix.
Adding the compatible flag will allow downstream projects to use versions compatible with the version declared in this projects package.json.