chore: improve build robustness - #194
Merged
Merged
Conversation
- add package-lock.json - add dependency update test to CI
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.
Over the last few years the builds have sometimes been broken by in-range updates to dependencies, especially development dependencies. Add
package-lock.jsonto make the build more reliable. To reduce the risk of missing breakages introduced by updates to production dependencies (which will affect cliui users), added a CI job which updates the direct dependencies then runs the tests.(Does not update dependencies, or bump required node, or pin GitHub actions... Other maintenance coming separately!)