chore(deps): update pnpm to v7.27.0 #3747
Merged
Conversation
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
trpc-bot
approved these changes
Feb 8, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 contains the following updates:
7.26.3->7.27.0Release Notes
pnpm/pnpm
v7.27.0Compare Source
Minor Changes
resolution-modeadded:lowest-direct. With this resolution mode direct dependencies will be resolved to their lowest versions. So if there isfoo@^1.1.0in the dependencies, then1.1.0will be installed, even if the latest version offoois1.2.0.pnpm run /build:.*/and execute the matched scripts with the RegExp #5871.Patch Changes
Fix version number replacing for namespaced workspace packages.
workspace:@​foo/bar@*should be replaced withnpm:@​foo/bar@<version>on publish #6052.When resolving dependencies, prefer versions that are already used in the root of the project. This is important to minimize the number of packages that will be nested during hoisting #6054.
Deduplicate direct dependencies.
Let's say there are two projects in the workspace that dependend on
foo. One project hasfoo@1.0.0in the dependencies while another one hasfoo@^1.0.0in the dependencies. In this case,foo@1.0.0should be installed to both projects as satisfies the version specs of both projects.Use Map rather than Object in
createPackageExtenderto prevent read the prototype property to native functionOur Gold Sponsors
Our Silver Sponsors
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.