Update pnpm to v7.2.1

[openverse-bot]

This PR contains the following updates:

Package	Type	Update	Change
pnpm (source)	packageManager	minor	7.1.0 -> 7.2.1

---

Release Notes

pnpm/pnpm

v7.2.1

Compare Source

Patch Changes

• Support Node.js from v14.6.
• Don't fail when the cafile setting is specified #​4877. This fixes a regression introduced in pnpm v7.2.0.

Our Sponsors

#### What's Changed * fix: support Node.js v14.6 by @​zkochan in https://github.com/pnpm/pnpm/pull/4878

Full Changelog: pnpm/pnpm@v7.2.0...v7.2.1

v7.2.0

Compare Source

Minor Changes

• A new setting is supported for ignoring specific deprecation messages: pnpm.allowedDeprecatedVersions. The setting should be provided in the pnpm section of the root package.json file. The below example will mute any deprecation warnings about the request package and warnings about express v1:

  {
    "pnpm": {
      "allowedDeprecatedVersions": {
        "request": "*",
        "express": "1"
      }
    }
  }

  Related issue: #​4306
  Related PR: #​4864

Patch Changes

• Update the compatibility database.
• Report only the first occurrence of a deprecated package.
• Add better hints to the peer dependency issue errors.

Our Sponsors

#### What's Changed * fix(setup): use @​pnpm/os.env.path-extender by @​zkochan in https://github.com/pnpm/pnpm/pull/4862 * fix: don't report the same deprecated package multiple times by @​zkochan in https://github.com/pnpm/pnpm/pull/4863 * feat: allowed deprecated versions by @​zkochan in https://github.com/pnpm/pnpm/pull/4864 * fix: add better peer dep error hints by @​zkochan in https://github.com/pnpm/pnpm/pull/4875

Full Changelog: pnpm/pnpm@v7.1.9...v7.2.0

v7.1.9

Compare Source

Patch Changes

• When the same package is found several times in the dependency graph, correctly autoinstall its missing peer dependencies at all times #​4820.

Our Sponsors

#### What's Changed * fix: auto-install-peers by @​zkochan in https://github.com/pnpm/pnpm/pull/4855

Full Changelog: pnpm/pnpm@v7.1.8...v7.1.9

v7.1.8

Compare Source

Patch Changes

• Suggest updating using Corepack, when pnpm was installed via Corepack.
• It should be possible to install a git-hosted package that has no package.json file #​4822.
• Fix pre-compiled pnpm binaries crashing when NODE_MODULES is set.

Our Sponsors

#### What's Changed * fix: pnpm pre-compiled binaries crash when NODE_MODULES is set by @​gluxon in https://github.com/pnpm/pnpm/pull/4823 * refactor(lockfile-file): Abstract LockfileFile to Lockfile conversion by @​gluxon in https://github.com/pnpm/pnpm/pull/4824 * test: update Jest by @​zkochan in https://github.com/pnpm/pnpm/pull/4644 * fix(cli): suggest to update with Corepack by @​zkochan in https://github.com/pnpm/pnpm/pull/4854 * fix: resolve manifest promise when manifest is not found by @​zkochan in https://github.com/pnpm/pnpm/pull/4826

Full Changelog: pnpm/pnpm@v7.1.7...v7.1.8

v7.1.7

Compare Source

Patch Changes

• Improve the performance of the build sequence calculation step #​4815.
• Correctly detect repeated dependency sequence during resolution #​4813.

Our Sponsors

#### What's Changed * fix: `pnpm add @​teambit/bit` should succeed by @​zkochan in https://github.com/pnpm/pnpm/pull/4813 * perf: build-modules by @​zkochan in https://github.com/pnpm/pnpm/pull/4815

Full Changelog: pnpm/pnpm@v7.1.6...v7.1.7

v7.1.6

Compare Source

Patch Changes

• Don't fail on projects with linked dependencies, when auto-install-peers is set to true #​4796.
• NODE_ENV=production pnpm install --dev should only install dev deps #​4745.

Our Sponsors

#### What's Changed * fix: only devDependencies are installed regardless of the node env by @​Spencer17x in https://github.com/pnpm/pnpm/pull/4805 * fix(auto-install-peers): don't fail on projects with linked deps by @​zkochan in https://github.com/pnpm/pnpm/pull/4807

Full Changelog: pnpm/pnpm@v7.1.5...v7.1.6

v7.1.5

Compare Source

Patch Changes

• Correctly detect the active Node.js version, when the pnpm CLI is bundled to an executable #​4203.

Our Sponsors

Full Changelog: pnpm/pnpm@v7.1.4...v7.1.5

v7.1.4

Compare Source

Patch Changes

• Correctly detect the active Node.js version, when the pnpm CLI is bundled to an executable #​4203.

Our Sponsors

#### What's Changed * fix: correctly detect the active Node.js version by @​zkochan in https://github.com/pnpm/pnpm/pull/4780

Full Changelog: pnpm/pnpm@v7.1.3...v7.1.4

v7.1.3

Compare Source

Patch Changes

• When auto-install-peers is set to true, automatically install missing peer dependencies without writing them to package.json as dependencies. This makes pnpm handle peer dependencies the same way as npm v7 #​4776.

Our Sponsors

#### What's Changed * chore: renovate bot setting to pin actions to a full length commit SHA by @​naveensrinivasan in https://github.com/pnpm/pnpm/pull/4768 * feat: auto install peer dependencies by @​zkochan in https://github.com/pnpm/pnpm/pull/4776 #### New Contributors * @​naveensrinivasan made their first contribution in https://github.com/pnpm/pnpm/pull/4768

Full Changelog: pnpm/pnpm@v7.1.2...v7.1.3

v7.1.2

Compare Source

Patch Changes

• pnpm setup should not fail on Windows if PNPM_HOME is not yet in the system registry #​4757
• pnpm dlx shouldn't modify the lockfile in the current working directory #​4743.

Our Sponsors

#### What's Changed * fix(setup): don't fail if PNPM_HOME is not yet in the system registry by @​zkochan in https://github.com/pnpm/pnpm/pull/4760 * fix(dlx): do not modify the lockfile in the cwd by @​zkochan in https://github.com/pnpm/pnpm/pull/4762

Full Changelog: pnpm/pnpm@v7.1.1...v7.1.2

v7.1.1

Compare Source

Patch Changes

• When the global bin directory is set to a symlink, check not only the symlink in the PATH but also the target of the symlink #​4744.
• Sanitize the directory names created inside node_modules/.pnpm and inside the global store #​4716
• All arguments after pnpm create <pkg> should be passed to the executed create app package. So pnpm create next-app --typescript should work`.
• Resolve commits from GitHub via https #​4734.

Our Sponsors

#### What's Changed * fix: sanitize dir names in the store by @​zkochan in https://github.com/pnpm/pnpm/pull/4726 * fix(create): pass all args to the executed create-app pkg by @​zkochan in https://github.com/pnpm/pnpm/pull/4730 * fix(git-resolver): resolve commits via https by @​zkochan in https://github.com/pnpm/pnpm/pull/4734 * refactor: setup by @​zkochan in https://github.com/pnpm/pnpm/pull/4731 * fix(config): checking global-bin-dir in PATH by @​zkochan in https://github.com/pnpm/pnpm/pull/4751

Full Changelog: pnpm/pnpm@v7.1.0...v7.1.1

---

Configuration

📅 Schedule: Branch creation - "before 3am on the first day of the month" (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, click this checkbox.

---

This PR has been generated by Renovate Bot.

[github-actions]

Storybook and Tailwind configuration previews: Updating
(This comment will be automatically updated with the preview URLs once they are ready)

[sarayourfriend]

It looks like the self-hosted version still isn't using the pnpm configuration script and TS version is being knocked back down 😢

[obulat]

Can we do the pnpm/ node updates manually, but keep renovate for other dependencies?

[sarayourfriend]

We could, but I'd really prefer if we figured out how to make Renovate work properly with the pnpm script. Even if we have to truly self-host it on an AWS instance or something it seems worth getting it working. Or we could use dependabot for pnpm dependencies for now and Renovate for the rest until we figure it out. That seems like probably the least uplift option that gets us into a manageable state for the time being without distracting us from some other higher value things than tinkering with Renovate.

[sarayourfriend]

Made an issue for us to do just that: WordPress/openverse#544

[sarayourfriend]

Made an issue for us to do just that: WordPress/openverse#544

[krysal]

Closing as this will not be addressed at the moment.

[openverse-bot]

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will now ignore this update (7.2.1). You will still receive a PR once a newer version is released, so if you wish to permanently ignore this dependency, please add it to the ignoreDeps array of your renovate config.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.