Closed renovate[bot] closed 3 months ago
Latest commit: |
9d7b37e
|
Status: | ✅ Deploy successful! |
Preview URL: | https://ad625d2c.unplugin-vue-router.pages.dev |
Branch Preview URL: | https://renovate-pnpm-9-x.unplugin-vue-router.pages.dev |
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/json-server@0.17.4, npm/mande@2.0.8, npm/nuxt@3.10.2
🚨 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 | Note | Source |
---|---|---|---|
Install scripts | npm/yorkie@2.0.0 |
| |
Install scripts | npm/protobufjs@7.2.6 |
| |
Install scripts | npm/vue-demi@0.14.7 |
|
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 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.
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.
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/foo@1.0.0
or ignore all packages with @SocketSecurity ignore-all
@SocketSecurity ignore npm/yorkie@2.0.0
@SocketSecurity ignore npm/protobufjs@7.2.6
@SocketSecurity ignore npm/vue-demi@0.14.7
This PR contains the following updates:
8.15.7
->9.0.6
Release Notes
pnpm/pnpm (pnpm)
### [`v9.0.6`](https://togithub.com/pnpm/pnpm/compare/v9.0.5...v9.0.6) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v9.0.5...v9.0.6) ### [`v9.0.5`](https://togithub.com/pnpm/pnpm/compare/v9.0.4...v9.0.5) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v9.0.4...v9.0.5) ### [`v9.0.4`](https://togithub.com/pnpm/pnpm/compare/v9.0.3...v9.0.4) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v9.0.3...v9.0.4) ### [`v9.0.3`](https://togithub.com/pnpm/pnpm/compare/v9.0.2...v9.0.3) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v9.0.2...v9.0.3) ### [`v9.0.2`](https://togithub.com/pnpm/pnpm/compare/v9.0.1...v9.0.2) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v9.0.1...v9.0.2) ### [`v9.0.1`](https://togithub.com/pnpm/pnpm/compare/v9.0.0...v9.0.1) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v9.0.0...v9.0.1) ### [`v9.0.0`](https://togithub.com/pnpm/pnpm/releases/tag/v9.0.0) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.15.7...v9.0.0) ##### 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](https://pnpm.io/installation#using-a-standalone-script) or install the `@pnpm/exe` package. - Configuration updates: - [`dedupe-injected-deps`](https://pnpm.io/npmrc#dedupe-injected-deps): enabled by default. - [`link-workspace-packages`](https://pnpm.io/npmrc#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](https://pnpm.io/workspaces#workspace-protocol-workspace). - [`hoist-workspace-packages`](https://pnpm.io/npmrc#hoist-workspace-packages): enabled by default. - [`enable-pre-post-scripts`](https://pnpm.io/cli/run#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](https://togithub.com/pnpm/pnpm/pull/7470). - Dependency resolution changes: - Correct resolution of peer dependencies that have their own peer dependencies. Related issue: [#7444](https://togithub.com/pnpm/pnpm/issues/7444). Related PR: [#7606](https://togithub.com/pnpm/pnpm/pull/7606). - Optional peer dependencies may be resolved from any packages in the dependency graph [#7830](https://togithub.com/pnpm/pnpm/pull/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](https://togithub.com/pnpm/pnpm/pull/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](https://togithub.com/pnpm/pnpm/issues/3083). - When installing git-hosted dependencies, only pick the files that would be packed with the package [#7638](https://togithub.com/pnpm/pnpm/pull/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](https://togithub.com/pnpm/pnpm/issues/4765). Related PR: [#7487](https://togithub.com/pnpm/pnpm/pull/7487). - `node-gyp` updated to version 10. - PowerShell completion support added [#7597](https://togithub.com/pnpm/pnpm/pull/7597). - Support `node-options` option inside `.npmrc` file when running scripts [#7596](https://togithub.com/pnpm/pnpm/issues/7596). - Added support for registry-scoped SSL configurations (cert, key, and ca). Three new settings supported: `Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (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.