deps: bump core deps and devDeps#572
Merged
Merged
Conversation
Collaborator
Author
Poll! 🙋How granular do you like our git log to be? Vote by reacting.
|
Merged
naugtur
approved these changes
May 16, 2023
Member
|
Does this mean PR squashing from now on? 😍 |
Collaborator
Author
|
@weizman "these commits" here would refer to specifically this situation. It would still be on a case-by-case basis and this is one step on figuring out where to draw the line (in this case I merged them independently but would first squash into 1-3 before doing a rebase-merge in a future identical situation). |
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
3 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.
core/deps:merge-deep@^3.0.2->^3.0.3core/deps:json-stable-stringify@^1.0.1->^1.0.2core/devDeps:ses@^0.17.0->^0.18.4ses, wherecorewas on the older0.17.0.core/devDeps:tmp-promise@^3.0.2->^3.0.3