Update dependency @pnpm/audit to v1001

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@pnpm/audit (source)	7.0.19 -> 1001.0.4

---

Release Notes

pnpm/pnpm (@​pnpm/audit)

v8.2.0

Minor Changes

• Allow env variables to be specified with default values in .npmrc. This is a convention used by Yarn too.
  Using ${NAME-fallback} will return fallback if NAME isn't set. ${NAME:-fallback} will return fallback if NAME isn't set, or is an empty string #​6018.

Patch Changes

• Add -g to mismatch registries error info when original command has -g option #​6224.
• Don't fail with EBUSY error when trying to copy a file from the store #​6201
• pnpm config get <key> should print boolean values #​6360
• Don't print an info message about linked dependencies if they are real linked dependencies specified via the link: protocol in package.json #​6372

Our Gold Sponsors

Our Silver Sponsors

v8.1.1

Compare Source

Patch Changes

• Repeat installation should work on a project that has a dependency with parentheses in the scope name #​6348.
• Error summary should be reported as expected.
• Update @yarnpkg/shell to fix issues in the shell emulator #​6320.
• Installation should not fail when there is a local dependency in a directory that starts with the @ character #​6332.
• Registries are now passed to the preResolution hook.

Our Gold Sponsors

Our Silver Sponsors

v8.1.0

Minor Changes

• A new setting has been added called dedupe-direct-deps, which is disabled by default. When set to true, dependencies that are already symlinked to the root node_modules directory of the workspace will not be symlinked to subproject node_modules directories. This feature was enabled by default in v8.0.0 but caused issues, so it's best to disable it by default #​6299.
• Add ignore-workspace-cycles to silence workspace cycle warning #​6308.

Patch Changes

• Print the right lowest supported Node.js version in the error message, when pnpm is executed with an old Node.js version #​6297.
• Improve the outdated lockfile error message #​6304.

Our Gold Sponsors

Our Silver Sponsors

v8.0.0

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/exe package.

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 to rolling by default.
• resolution-mode: set to lowest-direct by 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-dependents resolved many such problems. With these new defaults, pnpm will face significantly fewer issues during migration from other package managers.

Lockfile Modifications

• Lockfile v6 is adopted. This new format improves the readability of the lockfile by removing hashes from package IDs. It also has some rearrangement of fields in the importers section. The new pnpm-lock.yaml file is more resistant to git merge conflicts!
• The registry field is removed from the resolution object in pnpm-lock.yaml.
• A lockfile is generated even for projects with no dependencies.

Other Changes

• When there's a files field in the package.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 the deploy-all-files setting to true (Related issue #​5911).
• Direct dependencies are deduped. If a dependency is present in both a project and the workspace root, it will only be linked to the workspace root.

Migration Instructions

Before updating pnpm to v8 in your CI, regenerate your pnpm-lock.yaml. To upgrade your lockfile, run pnpm install and 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

---

Configuration

📅 Schedule: Branch creation - "after 9am on Wednesday" in timezone Europe/London, 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 was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

[15:43:11.566] INFO (983): Installing npm pnpm@8.10.2...
[15:43:12.902] WARN (983): Npm error:
npm info using npm@10.8.2
npm info using node@v18.20.5
npm http fetch GET 200 https://registry.npmjs.org/pnpm 247ms (cache miss)
npm error code ECONNRESET
npm error network aborted
npm error network This is a problem related to network connectivity.
npm error network In most cases you are behind a proxy or have bad network settings.
npm error network
npm error network If you are behind a proxy, please make sure that the
npm error network 'proxy' config is set properly.  See: 'npm help config'
npm error A complete log of this run can be found in: /tmp/containerbase-npm-PM4IQ7/_logs/2025-01-08T15_43_11_748Z-debug-0.log
[15:43:12.913] ERROR (983): npm install command failed
[15:43:12.914] FATAL (983): Install tool pnpm failed in 1.3s.