-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update pnpm to v7 - autoclosed #52
Closed
Closed
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
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
4 times, most recently
from
May 18, 2022 19:55
aa07cd0
to
b240fa1
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
4 times, most recently
from
May 24, 2022 01:22
b47b91e
to
03923c0
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
3 times, most recently
from
May 30, 2022 10:42
7c0bd43
to
ce8bca2
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
5 times, most recently
from
June 11, 2022 03:31
d18ea70
to
a9a8ba7
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
2 times, most recently
from
June 19, 2022 00:35
c4f9125
to
908c1b5
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
4 times, most recently
from
July 2, 2022 16:14
03d904b
to
72d852f
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
2 times, most recently
from
July 12, 2022 00:13
6b55934
to
0aa28ea
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
3 times, most recently
from
July 22, 2022 12:45
b0f1be5
to
2e02c01
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
2 times, most recently
from
July 30, 2022 11:01
bf947fd
to
386258a
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
3 times, most recently
from
August 23, 2022 08:29
a522a79
to
bdfe191
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
August 24, 2022 13:32
bdfe191
to
ce1000f
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
2 times, most recently
from
September 5, 2022 19:27
fcd9479
to
9197739
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
4 times, most recently
from
September 23, 2022 01:23
d1ebb82
to
f8b3b5b
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
4 times, most recently
from
October 9, 2022 15:05
7be8192
to
96fc8e3
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
4 times, most recently
from
October 17, 2022 09:33
d2aa690
to
f7df6e8
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7
chore(deps): update pnpm to v7 - autoclosed
Oct 20, 2022
renovate
bot
changed the title
chore(deps): update pnpm to v7 - autoclosed
chore(deps): update pnpm to v7
Oct 20, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
October 20, 2022 15:25
f7df6e8
to
22b86d1
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
October 22, 2022 15:30
22b86d1
to
881f4f4
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7
chore(deps): update pnpm to v7 - autoclosed
Oct 24, 2022
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
->7.14.0
Release Notes
pnpm/pnpm
v7.14.0
Compare Source
Minor Changes
pnpm doctor
command to do checks for known common issuesPatch Changes
Ignore the
always-auth
setting.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
:Our Gold Sponsors
Our Silver Sponsors
v7.13.6
Compare Source
Patch Changes
@pnpm/npm-conf
to remove annoying builtin warning #5518.pnpm link --global <pkg>
should not change the type of the dependency #5478.pnpm outdated
command fails, print in which directory it failed.Our Gold Sponsors
Our Silver Sponsors
v7.13.5
Compare Source
Patch Changes
pnpm outdated
should work when the package tarballs are hosted on a domain that differs from the registry's domain #5492.strict-peer-dependencies
is set tofalse
by default.Our Gold Sponsors
Our Silver Sponsors
v7.13.4
Compare Source
Patch Changes
pnpm link <pkg> --global
should work when a custom target directory is specified with the--dir
CLI option #5473.Our Gold Sponsors
Our Silver Sponsors
v7.13.3
Compare Source
Patch Changes
auto-install-peers
is set totrue
and installation is done on a workspace with that has the same dependencies in multiple projects #5454.pnpm link --help
#5461.install
,update
,add
, andremove
#1021.pnpm pack
, when a custom destination directory is used #5471.Our Gold Sponsors
Our Silver Sponsors
v7.13.2
Compare Source
Patch Changes
When linking commands to a directory, remove any .exe files that are already present in that target directory by the same name.
This fixes an issue with pnpm global update on Windows. If pnpm was installed with the standalone script and then updated with pnpm using
pnpm add --global pnpm
, the exe file initially created by the standalone script should be removed.When a direct dependency fails to resolve, print the path to the project directory in the error message.
pnpm patch-commit
should work when the patch directory is specified with a trailing slash #5449.Our Gold Sponsors
Our Silver Sponsors
v7.13.1
Compare Source
Patch Changes
pnpm update --interactive
should not list dependencies ignored via thepnpm.updateConfig.ignoreDependencies
setting.Our Gold Sponsors
Our Silver Sponsors
v7.13.0
Compare Source
Minor Changes
Ignore packages listed in
package.json
>pnpm.updateConfig.ignoreDependencies
fields on update/outdated command #5358For instance, if you don't want
webpack
automatically to be updated when you runpnpm update --latest
, put this to yourpackage.json
:Patterns are also supported, so you may ignore for instance any packages from a scope:
@babel/*
.It is possible now to update all dependencies except the listed ones using
!
. For instance, update all dependencies, exceptlodash
:It also works with pattends, for instance:
And it may be combined with other patterns:
Patch Changes
Hooks should be applied on
pnpm deploy
#5306.Stop
--filter-prod
option to run command on all the projects when used on workspace.--filter-prod
option now only filter fromdependencies
and omitdevDependencies
instead of including all the packages when used on workspace. So what was happening is that if you use--filter-prod
on workspace root like this:it was printing all the package of workspace, where it should only print the package name of itself and packages where it has been added as
dependency
(not asdevDependencies
)Don't override the root dependency when auto installing peer dependencies #5412.
Our Gold Sponsors
Our Silver Sponsors
What's Changed
package.json > pnpm.updateConfig.ignoreDependencies
on update/outdated commands by @Shinyaigehttps://github.com/pnpm/pnpm/pull/5408l/5408New Contributors
Full Changelog: pnpm/pnpm@v7.12.2...v7.13.0
v7.12.2
Compare Source
Patch Changes
pnpm link --global
should work with the--dir=<path>
option #5371.Our Gold Sponsors
Our Silver Sponsors
What's Changed
New Contributors
Full Changelog: pnpm/pnpm@v7.12.1...v7.12.2
v7.12.1
Compare Source
Patch Changes
Our Gold Sponsors
Our Silver Sponsors
What's Changed
Full Changelog: pnpm/pnpm@v7.12.0...v7.12.1
v7.12.0
Compare Source
Minor Changes
A new setting supported in the pnpm section of the
package.json
file:allowNonAppliedPatches
. When it is set totrue
, non-applied patches will not cause an error, just a warning will be printed. For example:Now it is possible to exclude packages from hoisting by prepending a
!
to the pattern. This works with both thehoist-pattern
andpublic-hoist-pattern
settings. For instance:Ref #5272
Patch Changes
pnpm patch
should work on files that don't have an end of line #5320.pnpm patch
using a custom--edit-dir
.Our Gold Sponsors
Our Silver Sponsors
What's Changed
New Contributors
Full Changelog: pnpm/pnpm@v7.11.0...v7.12.0
v7.11.0
Compare Source
Minor Changes
pnpm patch
: edit the patched package in a directory specified by the--edit-dir
option. E.g.,pnpm patch express@3.1.0 --edit-dir=/home/xxx/src/patched-express
#5304Patch Changes
Our Gold Sponsors
Our Silver Sponsors
What's Changed
New Contributors
Full Changelog: pnpm/pnpm@v7.10.0...v7.11.0
v7.10.0
Compare Source
Minor Changes
New time-based resolution strategy supported.
When
resolution-mode
is set totime-based
, pnpm will resolve dependencies the following way:foo@^1.1.0
in the dependencies, then1.1.0
will be installed.With this resolution mode installations with hot cache are faster. It also reduces the chance of subdependency hijacking as subdependencies will be updated only if direct dependencies are updated.
This resolution mode works only with npm's full metadata. So it is slower in some scenarios. However, if you use Verdaccio v5.15.1 or newer, you may set the
registry-supports-time-field
setting totrue
, and it will be really fast.Related RFC.
Enhance
pnpm env
with theremove
command. To remove a Node.js version installed by pnpm, run:Patch Changes
pnpm store prune
should remove all cached metadata.Our Gold Sponsors
Our Silver Sponsors
What's Changed
New Contributors
Full Changelog: pnpm/pnpm@v7.9.5...v7.10.0
v7.9.5
Compare Source
Patch Changes
NODE_PATH
whenprefer-symlinked-executables
is enabled #5251.node_modules
, even if the target directory doesn't exist #5219.Our Gold Sponsors
Our Silver Sponsors
What's Changed
New Contributors
Full Changelog: pnpm/pnpm@v7.9.4...v7.9.5
v7.9.4
Compare Source
Patch Changes
pnpm env
: for Node.js<16 install the x64 build on Darwin ARM as ARM build is not available #5239.pnpm env
: log a message when the node.js tarball starts the download #5241.pnpm install --merge-git-branch-lockfile
when the lockfile is up to date #5212.Our Gold Sponsors
Our Silver Sponsors
What's Changed
New Contributors
Full Changelog: pnpm/pnpm@v7.9.3...v7.9.4
v7.9.3
Compare Source
Patch Changes
Our Gold Sponsors
Our Silver Sponsors
What's Changed
Full Changelog: pnpm/pnpm@v7.9.2...v7.9.3
v7.9.2
Compare Source
Patch Changes
Our Gold Sponsors
Our Silver Sponsors
v7.9.1
Compare Source
Patch Changes
pnpm setup
: don't usesetx
to set env variables on Windows.Our Gold Sponsors
Our Silver Sponsors
v7.9.0
Compare Source
Minor Changes
ignore-dep-scripts
istrue
, ignore scripts of dependencies but run the scripts of the project.ignore-compatibility-db
is set totrue
, the compatibility database will not be used to patch dependencies [#5132](https:/Configuration
📅 Schedule: Branch creation - "before 3am on Monday" (UTC), 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.