chore(deps): update pnpm to v8 #75
Conversation
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/pnpm-8.x
branch
2 times, most recently
from
77326b8 to
fbfdf26
Compare
renovate
bot
force-pushed
the
renovate/pnpm-8.x
branch
2 times, most recently
from
d08dd38 to
e8cfdf8
Compare
renovate
bot
force-pushed
the
renovate/pnpm-8.x
branch
2 times, most recently
from
83229fe to
d0fbe64
Compare
renovate
bot
force-pushed
the
renovate/pnpm-8.x
branch
2 times, most recently
from
ea7649d to
751a8ca
Compare
renovate
bot
force-pushed
the
renovate/pnpm-8.x
branch
2 times, most recently
from
209eb84 to
3b2b217
Compare
renovate
bot
force-pushed
the
renovate/pnpm-8.x
branch
from
3b2b217 to
bf37960
Compare
renovate
bot
force-pushed
the
renovate/pnpm-8.x
branch
from
bf37960 to
9bfa001
Compare
🦋 Changeset detectedLatest commit: ca5014c The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. ⚠ Warning: custom changes will be lost. |
Codecov ReportPatch coverage:
❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more. Additional details and impacted files@@ Coverage Diff @@
## master #75 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 15 15
Lines 148 154 +6
Branches 17 23 +6
=========================================
+ Hits 148 154 +6
☔ View full report in Codecov by Sentry. |
This PR contains the following updates:
7.30.5->8.6.1Release Notes
pnpm/pnpm
v8.6.1Compare Source
Patch Changes
When
dedupe-peer-dependentsis enabled (default), use the path (not id) to determine compatibility.When multiple dependency groups can be deduplicated, the latter ones are sorted according to number of peers to allow them to benefit from deduplication.
Resolves: #6605
Some minor performance improvements by removing await from loops #6617.
Our Gold Sponsors
Our Silver Sponsors
v8.6.0Compare Source
Minor Changes
Some settings influence the structure of the lockfile, so we cannot reuse the lockfile if those settings change. As a result, we need to store such settings in the lockfile. This way we will know with which settings the lockfile has been created.
A new field will now be present in the lockfile:
settings. It will store the values of two settings:autoInstallPeersandexcludeLinksFromLockfile. If someone tries to perform afrozen-lockfileinstallation and their active settings don't match the ones in the lockfile, then an error message will be thrown.The lockfile format version is bumped from v6.0 to v6.1.
Related PR: #6557
Related issue: #6312
A new setting,
exclude-links-from-lockfile, is now supported. When enabled, specifiers of local linked dependencies won't be duplicated in the lockfile.This setting was primarily added for use by Bit CLI, which links core aspects to
node_modulesfrom external directories. As such, the locations may vary across different machines, resulting in the generation of lockfiles with differing locations.Patch Changes
npm:foo@1.0.0becomesnpm:foo@1.1.0.workspace:protocol is not found in the workspace #4477.pnpm rebuildshould not fail whennode-linkeris set tohoistedand there are skipped optional dependencies #6553.Our Gold Sponsors
Our Silver Sponsors
v8.5.1Compare Source
Patch Changes
package.jsonfile(s), print out what are the differences #6536.Our Gold Sponsors
Our Silver Sponsors
v8.5.0Compare Source
Minor Changes
pnpm patch-removecommand added #6521.Patch Changes
pnpm link -g <pkg-name>should not modify thepackage.jsonfile #4341.node_modulesdirectory #6510.enginesfield should match prerelease versions #6509.Our Gold Sponsors
Our Silver Sponsors
v8.4.0Compare Source
Minor Changes
pnpm publishsupports the--provenanceCLI option #6435.Patch Changes
node-linkeris set tohoisted6486.node_modulesdirectory unless the--forceoption is passed.node_modulesfolder with a.modules.yamlfile if there are no dependencies insidenode_modules.Our Gold Sponsors
Our Silver Sponsors
v8.3.1Compare Source
Patch Changes
node-fetchto fix an error that happens on Node.js 20 #6424.Our Gold Sponsors
Our Silver Sponsors
v8.3.0Compare Source
Minor Changes
pnpm packcommand using thepack-gzip-levelsetting #6393.--checkflag topnpm dedupe. No changes will be made tonode_modulesor the lockfile. Exits with a non-zero status code if changes are possible.pnpm install --resolution-onlyre-runs resolution to print out any peer dependency issues #6411.Patch Changes
publishConfig.directoryof an injected workspace dependency does not exist #6396.Our Gold Sponsors
Our Silver Sponsors
v8.2.0Compare Source
Minor Changes
.npmrc. This is a convention used by Yarn too.Using
${NAME-fallback}will returnfallbackifNAMEisn't set.${NAME:-fallback}will returnfallbackifNAMEisn't set, or is an empty string #6018.Patch Changes
-gto mismatch registries error info when original command has-goption #6224.pnpm config get <key>should print boolean values #6360link:protocol inpackage.json#6372Our Gold Sponsors
Our Silver Sponsors
v8.1.1Compare Source
Patch Changes
@yarnpkg/shellto fix issues in the shell emulator #6320.@character #6332.preResolutionhook.Our Gold Sponsors
Our Silver Sponsors
v8.1.0Compare Source
Minor Changes
dedupe-direct-deps, which is disabled by default. When set totrue, dependencies that are already symlinked to the rootnode_modulesdirectory of the workspace will not be symlinked to subprojectnode_modulesdirectories. This feature was enabled by default in v8.0.0 but caused issues, so it's best to disable it by default #6299.ignore-workspace-cyclesto silence workspace cycle warning #6308.Patch Changes
Our Gold Sponsors
Our Silver Sponsors
v8.0.0Compare Source
We are excited to announce the latest release of pnpm! To install it, check the installation page.
Major Changes
Node.js 14 Support Discontinued
If you still require Node.js 14, don't worry. We ship pnpm bundled with Node.js. This means that regardless of which Node.js version you've installed, pnpm will operate using the necessary Node.js runtime. For this to work you need to install pnpm either using the standalone script or install the
@pnpm/exepackage.Configuration Updates
auto-install-peers: enabled by default.dedupe-peer-dependents: enabled by default.resolve-peers-from-workspace-root: enabled by default.save-workspace-protocol: set torollingby default.resolution-mode: set tolowest-directby default.publishConfig.linkDirectory: enabled by default.Most of the configuration changes are related to peer dependencies. Most of these settings were implemented long ago, and we recommended them to users encountering peer dependency issues. The recently added
dedupe-peer-dependentsresolved many such problems. With these new defaults, pnpm will face significantly fewer issues during migration from other package managers.Lockfile Modifications
importerssection. The newpnpm-lock.yamlfile is more resistant to git merge conflicts!resolutionobject inpnpm-lock.yaml.Other Changes
filesfield in thepackage.json, only the files that are listed in it will be deployed. The same logic is applied when injecting packages. This behaviour can be changed by setting thedeploy-all-filessetting totrue(Related issue #5911).Migration Instructions
Before updating pnpm to v8 in your CI, regenerate your
pnpm-lock.yaml. To upgrade your lockfile, runpnpm installand commit the changes. Existing dependencies will not be updated; however, due to configuration changes in pnpm v8, some missing peer dependencies may be added to the lockfile and some packages may get deduplicated.You can commit the new lockfile even before upgrading Node.js in the CI, as pnpm v7 already supports the new lockfile format.
pnpm v7 Support
pnpm v7 will likely not receive any new features, but it will continue to get bug fixes for a few months and vulnerability fixes for at least a year.
Our Gold Sponsors
Our Silver Sponsors
v7.33.0Compare Source
Minor Changes
Some settings influence the structure of the lockfile, so we cannot reuse the lockfile if those settings change. As a result, we need to store such settings in the lockfile. This way we will know with which settings the lockfile has been created.
A new field will now be present in the lockfile:
settings. It will store the values of two settings:autoInstallPeersandexcludeLinksFromLockfile. If someone tries to perform afrozen-lockfileinstallation and their active settings don't match the ones in the lockfile, then an error message will be thrown.The lockfile format version is bumped from v6.0 to v6.1.
Related PR: #6557
Related issue: #6312
Patch Changes
npm:foo@1.0.0becomesnpm:foo@1.1.0.workspace:protocol is not found in the workspace #4477.updateConfig.ignoreDependencies#6548Our Gold Sponsors
Our Silver Sponsors
Configuration
📅 Schedule: Branch creation - "after 1am and before 6am on the 1st through 3rd day of the month" in timezone Asia/Tokyo, 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.