-
Notifications
You must be signed in to change notification settings - Fork 12
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 v8 - autoclosed #45
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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #45 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 1 1
Lines 131 131
Branches 35 35
=========================================
Hits 131 131 ☔ View full report in Codecov by Sentry. |
renovate
bot
force-pushed
the
renovate/pnpm-8.x
branch
2 times, most recently
from
April 4, 2023 06:29
7f64754
to
1719256
Compare
renovate
bot
force-pushed
the
renovate/pnpm-8.x
branch
from
April 10, 2023 01:43
1719256
to
b10a4ce
Compare
renovate
bot
force-pushed
the
renovate/pnpm-8.x
branch
3 times, most recently
from
April 23, 2023 01:41
c8def2f
to
e777f2d
Compare
renovate
bot
force-pushed
the
renovate/pnpm-8.x
branch
from
May 2, 2023 13:56
e777f2d
to
2235f4c
Compare
renovate
bot
force-pushed
the
renovate/pnpm-8.x
branch
2 times, most recently
from
May 15, 2023 02:05
9b262fe
to
7300850
Compare
renovate
bot
force-pushed
the
renovate/pnpm-8.x
branch
2 times, most recently
from
June 5, 2023 14:51
e4d624e
to
0ab4772
Compare
renovate
bot
force-pushed
the
renovate/pnpm-8.x
branch
from
June 11, 2023 21:54
0ab4772
to
9753e3f
Compare
renovate
bot
force-pushed
the
renovate/pnpm-8.x
branch
3 times, most recently
from
June 26, 2023 13:34
6f7853c
to
7ce2523
Compare
renovate
bot
force-pushed
the
renovate/pnpm-8.x
branch
2 times, most recently
from
July 10, 2023 01:27
c4dbc58
to
af22879
Compare
renovate
bot
force-pushed
the
renovate/pnpm-8.x
branch
3 times, most recently
from
July 24, 2023 00:45
9d1e929
to
3268269
Compare
renovate
bot
force-pushed
the
renovate/pnpm-8.x
branch
2 times, most recently
from
August 6, 2023 12:14
2a40dc1
to
b3c6b5a
Compare
renovate
bot
force-pushed
the
renovate/pnpm-8.x
branch
2 times, most recently
from
August 31, 2023 19:19
ae5a231
to
e1974e9
Compare
renovate
bot
force-pushed
the
renovate/pnpm-8.x
branch
4 times, most recently
from
September 11, 2023 14:39
53f2b6f
to
37c1283
Compare
renovate
bot
force-pushed
the
renovate/pnpm-8.x
branch
from
September 17, 2023 20:26
37c1283
to
0dbc6c5
Compare
renovate
bot
force-pushed
the
renovate/pnpm-8.x
branch
from
September 26, 2023 16:03
0dbc6c5
to
ace2ea0
Compare
renovate
bot
force-pushed
the
renovate/pnpm-8.x
branch
3 times, most recently
from
October 16, 2023 00:11
6825527
to
81c3fad
Compare
renovate
bot
force-pushed
the
renovate/pnpm-8.x
branch
3 times, most recently
from
November 1, 2023 19:43
1addec3
to
ec88607
Compare
renovate
bot
force-pushed
the
renovate/pnpm-8.x
branch
2 times, most recently
from
November 13, 2023 18:07
d93a629
to
27d5572
Compare
renovate
bot
force-pushed
the
renovate/pnpm-8.x
branch
from
November 14, 2023 14:19
27d5572
to
192f487
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v8
chore(deps): update pnpm to v8 - autoclosed
Nov 15, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 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.
This PR contains the following updates:
7.32.2
->8.10.5
Release Notes
pnpm/pnpm (pnpm)
v8.10.5
Compare Source
Patch Changes
pnpm-workspace.yaml
file #7307.Our Gold Sponsors
Our Silver Sponsors
v8.10.4
Compare Source
Patch Changes
node-linker
was set tohoisted
#6227.Our Gold Sponsors
Our Silver Sponsors
v8.10.3
Compare Source
Patch Changes
(Important) Increased the default amount of allowed concurrent network request on systems that have more than 16 CPUs #7285.
pnpm patch
should reuse existing patch whenshared-workspace-file=false
#7252.Don't retry fetching missing packages, since the retries will never work #7276.
When using
pnpm store prune --force
alien directories are removed from the store #7272.Downgraded
npm-packlist
because the newer version significantly slows down the installation of local directory dependencies, making it unbearably slow.npm-packlist
was upgraded in this PR to fix #6997. We added our own file deduplication to fix the issue of duplicate file entries.Fixed a performance regression on running installation on a project with an up to date lockfile #7297.
Throw an error on invalid
pnpm-workspace.yaml
file #7273.Our Gold Sponsors
Our Silver Sponsors
v8.10.2
Compare Source
Patch Changes
Our Gold Sponsors
Our Silver Sponsors
v8.10.1
Compare Source
Patch Changes
pnpm-lock.yaml
will no longer contain aregistry
field. This field has been unused for a long time. This change should not cause any issues besides backward compatible modifications to the lockfile #7262.pnpm dlx
in the root of a Windows Drive #7263.@npmcli/arborist
to patch it with a fix #7269.Our Gold Sponsors
Our Silver Sponsors
v8.10.0
Compare Source
Minor Changes
Support for multiple architectures when installing dependencies #5965.
You can now specify architectures for which you'd like to install optional dependencies, even if they don't match the architecture of the system running the install. Use the
supportedArchitectures
field inpackage.json
to define your preferences.For example, the following configuration tells pnpm to install optional dependencies for Windows x64:
Whereas this configuration will have pnpm install optional dependencies for Windows, macOS, and the architecture of the system currently running the install. It includes artifacts for both x64 and arm64 CPUs:
Additionally,
supportedArchitectures
also supports specifying thelibc
of the system.The
pnpm licenses list
command now accepts the--filter
option to check the licenses of the dependencies of a subset of workspace projects #5806.Patch Changes
Allow scoped name as bin name #7112.
When running scripts recursively inside a workspace, the logs of the scripts are grouped together in some CI tools. (Only works with
--workspace-concurrency 1
)Print a warning when installing a dependency from a non-existent directory #7159
Should fetch dependency from tarball url when patching dependency installed from git #7196
pnpm setup
should add a newline at the end of the updated shell config file #7227.Improved the performance of linking bins of hoisted dependencies to
node_modules/.pnpm/node_modules/.bin
#7212.Wrongful ELIFECYCLE error on program termination #7164.
pnpm publish
should not pack the same file twice sometimes #6997.The fix was to update
npm-packlist
to the latest version.Our Gold Sponsors
Our Silver Sponsors
v8.9.2
Compare Source
Patch Changes
preinstall
lifecycle script is present #7206.Our Gold Sponsors
Our Silver Sponsors
v8.9.1
Compare Source
Patch Changes
pnpm update --interactive
7109shared-workspace-lockfile
is set tofalse
, read the pnpm settings frompackage.json
files that are nested. This was broken in pnpm v8.9.0 #7184.node_modules
on Windows Dev Drives #7186. This is a fix to a regression that was shipped with v8.9.0.pnpm dlx
should ignore any settings that are in apackage.json
file found in the current working directory #7198.Our Gold Sponsors
Our Silver Sponsors
v8.9.0
Compare Source
Minor Changes
🚀Performance improvement: Use reflinks instead of hard links by default on macOS and Windows Dev Drives #5001.
The list of packages that are allowed to run installation scripts now may be provided in a separate configuration file. The path to the file should be specified via the
pnpm.onlyBuiltDependenciesFile
field inpackage.json
. For instance:In the example above, the list is loaded from a dependency. The JSON file with the list should contain an array of package names. For instance:
With the above list, only
esbuild
and@reflink/reflink
will be allowed to run scripts during installation.Related issue: #7137.
Add
disallow-workspace-cycles
option to error instead of warn about cyclic dependenciesAllow
env rm
to remove multiple node versions at once, and introduceenv add
for installing node versions without setting as default #7155.Patch Changes
pnpm why
when the dependencies tree is too big, the command will now prune the tree to just 10 end leafs and now supports--depth
argument #7122.neverBuiltDependencies
andonlyBuiltDependencies
from the rootpackage.json
of the workspace, whenshared-workspace-lockfile
is set tofalse
#7141.pnpm.overrides
replacingresolutions
, the two are now merged. This is intended to make it easier to migrate from Yarn by allowing one to keep usingresolutions
for Yarn, but adding additional changes just for pnpm usingpnpm.overrides
.Our Gold Sponsors
Our Silver Sponsors
v8.8.0
Compare Source
Minor Changes
--reporter-hide-prefix
option forrun
command to hide project name as prefix for lifecycle log outputs of running scripts #7061.Patch Changes
--ignore-scripts
command to install, when runningpnpm dedupe --ignore-scripts
#7102.node-linker
is set tohoisted
, thepackage.json
files of the existing dependencies insidenode_modules
will be checked to verify their actual versions. The data in thenode_modules/.modules.yaml
andnode_modules/.pnpm/lock.yaml
may not be fully reliable, as an installation may fail after changes to dependencies were made but before those state files were updated #7107.Our Gold Sponsors
Our Silver Sponsors
v8.7.6
Compare Source
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.