chore: update dev dependencies #23
Open
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
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 was automatically generated to update versions of dev dependencies to their latest versions. This helps ensure we get fixes and improvements in a timely fashion and reduces the impact of updating the versions that can arise if versions are allowed to become stale for an extended period.
What did you change?
This action ran
yarn upgrade:automaticto updatepackage.jsonfiles to request the latest versions of each package. Certain critical packages are intentionally excluded.This action also deleted the
yarn.lockfile in order to recreate it with the latest matching versions of secondary dependencies.This PR includes the various
package.jsonthat pull our dependencies forward to the latest versions, theyarn.lockupdate that maps required versions to the actual versions to be used, and updates the offline mirror.How did you test and verify your work?
This PR should not normally significantly affect the build outputs or runtime packages. Ensure that
yarn ci-checkruns cleanly and all tests pass (done automatically as part of the PR checks).