Open
Conversation
|
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
d036d7d to
d76584e
Compare
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
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:
6.34.0->6.35.1Release Notes
pnpm/pnpm
v6.35.1Compare Source
Patch Changes
.npmrcfiles in subdirectories inside a workspace #2570.v6.35.0Compare Source
Patch Changes
Installing a package with
binthat points to an.exefile on Windows #5159.Ignore the
always-authsetting.pnpm will never reuse the registry auth token for requesting the package tarball, if the package tarball is hosted on a different domain.
So, for example, if your registry is at
https://company.registry.com/but the tarballs are hosted athttps://tarballs.com/, then you will have to configure the auth token for both domains in your.npmrc:When an error happens during installation of a subdependency, print some context information in order to be able to locate that subdependency. Print the exact chain of packages that led to the problematic dependency.
Configuration
📅 Schedule: Branch creation - "after 10pm every weekday,before 5am every weekday,every weekend" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.