Skip to content
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 v9 #2841

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): update pnpm to v9 #2841

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 22, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
pnpm (source) 8.15.5 -> 9.1.0 age adoption passing confidence

Release Notes

pnpm/pnpm (pnpm)

v9.1.0

Compare Source

v9.0.6

Compare Source

v9.0.5

Compare Source

v9.0.4

Compare Source

v9.0.3

Compare Source

v9.0.2

Compare Source

v9.0.1

Compare Source

v9.0.0

Compare Source

Major Changes
  • Node.js v16 support discontinued

    If you still require Node.js 16, 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/exe package.

  • Configuration updates:

    • dedupe-injected-deps: enabled by default.
    • link-workspace-packages: disabled by default. This means that by default, dependencies will be linked from workspace packages only when they are specified using the workspace protocol.
    • hoist-workspace-packages: enabled by default.
    • enable-pre-post-scripts: enabled by default.
    • Use the same directory for state files on macOS as on Linux (~/.local/state/pnpm).
    • pnpm will now check the package.json file for a packageManager field. If this field is present and specifies a different package manager or a different version of pnpm than the one you're currently using, pnpm will not proceed. This ensures that you're always using the correct package manager and version that the project requires.
  • Lockfile changes:

    • Lockfile v9 is adopted. This new format has changes for better readability, and better resistence to Git conflicts.
    • Support for lockfile v5 is dropped. Use pnpm v8 to convert lockfile v5 to lockfile v6 #​7470.
  • Dependency resolution changes:

    • Correct resolution of peer dependencies that have their own peer dependencies.
      Related issue: #​7444.
      Related PR: #​7606.
    • Optional peer dependencies may be resolved from any packages in the dependency graph #​7830.
  • pnpm licenses list prints license information of all versions of the same package in case different versions use different licenses. The format of the pnpm licenses list --json output has been changed #​7528.

  • A new command added for printing completion code to the console: pnpm completion [shell]. The old command that modified the user's shell dotfiles has been removed #​3083.

  • When installing git-hosted dependencies, only pick the files that would be packed with the package #​7638.

Minor Changes
  • It is now possible to install only a subdirectory from a Git repository.

    For example, pnpm add github:user/repo#path:packages/foo will add a dependency from the packages/foo subdirectory.

    This new parameter may be combined with other supported parameters separated by &. For instance, the next command will install the same package from the dev branch: pnpm add github:user/repo#dev&path:packages/bar.

    Related issue: #​4765.
    Related PR: #​7487.

  • node-gyp updated to version 10.

  • PowerShell completion support added #​7597.

  • Support node-options option inside .npmrc file when running scripts #​7596.

  • Added support for registry-scoped SSL configurations (cert, key, and ca). Three new settings supported: <registryURL>:certfile, <registryURL>:keyfile, and <registryURL>:ca. For instance:

    //registry.mycomp.com/:certfile=server-cert.pem
    //registry.mycomp.com/:keyfile=server-key.pem
    //registry.mycomp.com/:cafile=client-cert.pem
    

    Related issue: #​7427.
    Related PR: #​7626.

  • Add a field named ignoredOptionalDependencies. This is an array of strings. If an optional dependency has its name included in this array, it will be skipped #​7714.

  • The checksum of the .pnpmfile.cjs is saved into the lockfile. If the pnpmfile gets modified, the lockfile is reanalyzed to apply the changes #​7662.

  • Added cache for pnpm dlx #​5277.

Patch Changes
  • Package tarballs are not downloaded during --lockfile-only installation #​1328.
  • Peer dependency rules should only affect reporting, not data in the lockfile #​7758.
  • Link overrides should be able to use absolute path #​7749.
  • pnpm dlx should not read settings from the current working directory #​7916.
Platinum Sponsors
Gold Sponsors
Our Silver Sponsors

v8.15.8

Compare Source

v8.15.7

Compare Source

v8.15.6

Compare Source

Patch Changes

  • The exit code of the child process should be preserved on pnpm run #​7817.
  • When sorting packages in a workspace, take into account workspace dependencies specified as peerDependencies #​7813.
  • Add --ignore-scripts argument to prune command #​7836.

Platinum Sponsors

Gold Sponsors

Silver Sponsors


Configuration

📅 Schedule: Branch creation - "before 4am 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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added the c: dependencies Pull requests that adds/updates a dependency label Apr 22, 2024
Copy link

stackblitz bot commented Apr 22, 2024

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

Copy link

netlify bot commented Apr 22, 2024

Deploy Preview for elk-zone ready!

Name Link
🔨 Latest commit 915bc8d
🔍 Latest deploy log https://app.netlify.com/sites/elk-zone/deploys/6638bbf6184fe10008ebf56d
😎 Deploy Preview https://deploy-preview-2841--elk-zone.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link

netlify bot commented Apr 22, 2024

Deploy Preview for elk-docs canceled.

Name Link
🔨 Latest commit 915bc8d
🔍 Latest deploy log https://app.netlify.com/sites/elk-docs/deploys/6638bbf655f44f00080f199b

Copy link

socket-security bot commented Apr 22, 2024

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/@antfu/[email protected] environment Transitive: eval, filesystem, shell, unsafe +61 17.6 MB antfu
npm/@iconify/[email protected] filesystem +1 350 MB cyberalien
npm/@iconify/[email protected] Transitive: environment, filesystem, shell +22 1.47 MB cyberalien
npm/@nuxt/[email protected] environment, network Transitive: eval, filesystem, shell, unsafe +73 33.9 MB antfu
npm/@nuxt/[email protected] Transitive: environment, eval, filesystem, network, shell, unsafe +49 17 MB danielroe
npm/@nuxtjs/[email protected] Transitive: environment, filesystem, unsafe +24 3.89 MB danielroe
npm/@tiptap/[email protected] None 0 23.8 kB _bdbch
npm/@unlazy/[email protected] Transitive: environment, filesystem, unsafe +24 3.88 MB johannschopplich
npm/@upstash/[email protected] environment, network 0 276 kB hezarfen
npm/@vue-macros/[email protected] Transitive: environment, filesystem, unsafe +24 3.88 MB sxzz
npm/@vueuse/[email protected] None 0 35.5 kB antfu
npm/@vueuse/[email protected] Transitive: environment, filesystem, unsafe +25 3.9 MB antfu
npm/[email protected] None 0 20.9 kB antfu
npm/[email protected] None 0 17.1 kB mottie
npm/[email protected] eval, filesystem, network, shell, unsafe 0 6.56 MB davidortner
npm/[email protected] None 0 53.8 kB jaffathecake
npm/[email protected] filesystem, shell 0 7.5 kB douglasjunior
npm/[email protected] None 0 36.3 kB meikidd
npm/[email protected] None 0 405 kB vitaly
npm/[email protected] Transitive: environment, filesystem, shell +10 354 kB okonet
npm/[email protected] None 0 458 kB isaacs
npm/[email protected] network 0 457 kB neetshin
npm/[email protected] None 0 59.8 kB omnidan
npm/[email protected] Transitive: environment, filesystem, unsafe +24 3.9 MB baroshem
npm/[email protected] Transitive: environment, eval, filesystem, network, shell, unsafe +45 11.3 MB danielroe
npm/[email protected] None 0 131 kB philipwalton
npm/[email protected] environment Transitive: eval, filesystem, unsafe +3 4.99 MB posva
npm/[email protected] None 0 13.9 kB ai
npm/[email protected] environment, filesystem, unsafe 0 8.39 MB prettier-bot
npm/[email protected] None 0 24.5 kB ocavue
npm/[email protected] environment, unsafe 0 1.48 MB manucorporat
npm/[email protected] filesystem 0 11.5 kB ssnangua
npm/[email protected] environment +1 591 kB lovell
npm/[email protected] None 0 7.81 MB antfu
npm/[email protected] filesystem 0 10.9 kB toplenboren
npm/[email protected] shell Transitive: environment +1 989 kB steveukx
npm/[email protected] environment Transitive: eval, filesystem, unsafe +3 4.67 MB oikawa_rizumu
npm/[email protected] filesystem Transitive: environment, unsafe +25 3.95 MB sxzz
npm/[email protected] None 0 26.2 kB pi0
npm/[email protected] None 0 4.63 kB sindresorhus
npm/[email protected] None 0 147 kB antfu
npm/[email protected] None 0 3.51 kB natemoo-re
npm/[email protected] environment 0 2.07 MB atomiks
npm/[email protected] None 0 392 kB hirokiosame
npm/[email protected] None 0 32.4 MB typescript-bot
npm/[email protected] None 0 103 kB pi0
npm/[email protected] None 0 357 kB natemoo-re
npm/[email protected] Transitive: environment, filesystem +12 3.73 MB antfu
npm/[email protected] filesystem Transitive: environment, eval, network, shell, unsafe +4 6.2 MB userquin
npm/[email protected] environment, eval Transitive: filesystem, network, shell, unsafe +18 8.32 MB vitestbot
npm/[email protected] Transitive: environment, eval, filesystem, unsafe +3 4.99 MB norserium
npm/[email protected] None +1 99.2 kB johnsoncodehk
npm/[email protected] Transitive: environment, eval, filesystem, unsafe +3 5.1 MB akryum
npm/[email protected] filesystem Transitive: environment +1 2.74 MB tropicadri
npm/[email protected] environment 0 577 kB tropicadri
npm/[email protected] environment, network 0 141 kB lpinca

🚮 Removed packages: npm/[email protected], npm/[email protected]

View full report↗︎

Copy link

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert Package NoteSource
Install scripts npm/[email protected]
  • Install script: install
  • Source: node install/check
Install scripts npm/[email protected]
  • Install script: postinstall
  • Source: node ./postinstall.js

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c: dependencies Pull requests that adds/updates a dependency
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants