chore(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Type	Update	Change	Age	Adoption	Passing	Confidence
actions/setup-node	action	minor	v3.6.0 -> v3.7.0
pnpm (source)	packageManager	minor	7.30.5 -> 7.33.6
pnpm/action-setup	action	minor	v2.2.4 -> v2.4.0
vitest	devDependencies	minor	^0.29.0 -> ^0.34.0

---

Release Notes

actions/setup-node (actions/setup-node)

v3.7.0

Compare Source

What's Changed

In scope of this release we added a logic to save an additional cache path for yarn 3 (related pull request and feature request). Moreover, we added functionality to use all the sub directories derived from cache-dependency-path input and add detect all dependencies directories to cache (related pull request and feature request).

Besides, we made such changes as:

• Replace workflow badge with new badge by @​jongwooo in https://github.com/actions/setup-node/pull/653
• Fix a minor typo by @​phanan in https://github.com/actions/setup-node/pull/662
• docs: fix typo in advanced-usage.md by @​remarkablemark in https://github.com/actions/setup-node/pull/697
• bugfix: Don't attempt to use Windows fallbacks on non-Windows OSes by @​domdomegg in https://github.com/actions/setup-node/pull/718
• Update to node 18.x by @​feelepxyz in https://github.com/actions/setup-node/pull/751
• Remove implicit dependencies by @​nikolai-laevskii in https://github.com/actions/setup-node/pull/758
• Fix description about ensuring workflow access to private package by @​x86chi in https://github.com/actions/setup-node/pull/704

New Contributors

• @​jongwooo made their first contribution in https://github.com/actions/setup-node/pull/653
• @​phanan made their first contribution in https://github.com/actions/setup-node/pull/662
• @​remarkablemark made their first contribution in https://github.com/actions/setup-node/pull/697
• @​domdomegg made their first contribution in https://github.com/actions/setup-node/pull/718
• @​feelepxyz made their first contribution in https://github.com/actions/setup-node/pull/751
• @​nikolai-laevskii made their first contribution in https://github.com/actions/setup-node/pull/758
• @​x86chi made their first contribution in https://github.com/actions/setup-node/pull/704

Full Changelog: actions/setup-node@v3...v3.7.0

pnpm/pnpm (pnpm)

v7.33.6

Compare Source

Patch Changes

• Authorization token should be found in the configuration, when the requested URL is explicitly specified with a default port (443 on HTTPS or 80 on HTTP) #​6863.

Our Gold Sponsors

Our Silver Sponsors

v7.33.5

Compare Source

Patch Changes

• Temporarily revert the fix to #​6805 to fix the regression it caused #​6827.

Our Gold Sponsors

Our Silver Sponsors

v7.33.4

Compare Source

Patch Changes

• When the same file is appended multiple times into a tarball, the last occurrence is selected when unpacking the tarball.
• Added support for publishConfig.registry in package.json for publishing #​6775.
• Fixed a bug in which pnpm passed the wrong scheme to git ls-remote, causing a fallback to git+ssh and resulting in a 'host key verification failed' issue #​6805

Our Gold Sponsors

Our Silver Sponsors

v7.33.3

Compare Source

Patch Changes

• Improve the performance of searching for auth tokens.
• Installation of a git-hosted dependency without package.json should not fail, when the dependency is read from cache #​6721.
• Local workspace bin files that should be compiled first are linked to dependent projects after compilation #​1801.
• Prefer versions found in parent package dependencies only #​6737.

Our Gold Sponsors

Our Silver Sponsors

v7.33.2

Compare Source

Patch Changes

• In cases where both aliased and non-aliased dependencies exist to the same package, non-aliased dependencies will be used for resolving peer dependencies, addressing issue #​6588.
• Don't crash when the APPDATA env variable is not set on Windows #​6659.
• Don't fail when a package is archived in a tarball with malformed tar headers #​5362.
• Peer dependencies of subdependencies should be installed, when node-linker is set to hoisted #​6680.
• Ignore the port in the URL, while searching for authentication token in the .npmrc file #​6354.
• Throw a meaningful error when applying a patch to a dependency fails.
• pnpm update --global --latest should work #​3779.

Our Gold Sponsors

Our Silver Sponsors

v7.33.1

Compare Source

Patch Changes

• When dedupe-peer-dependents is enabled, 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

• Change lockfile version back to 6.0 as previous versions of pnpm fail to parse the version correctly.

Our Gold Sponsors

Our Silver Sponsors

v7.33.0

Compare 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: autoInstallPeers and excludeLinksFromLockfile. If someone tries to perform a frozen-lockfile installation 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

• When updating dependencies, preserve the range prefix in aliased dependencies. So npm:foo@1.0.0 becomes npm:foo@1.1.0.
• Print a meaningful error when a project referenced by the workspace: protocol is not found in the workspace #​4477.
• Should respect ignore patterns in updateConfig.ignoreDependencies #​6548

Our Gold Sponsors

Our Silver Sponsors

v7.32.5

Compare Source

Patch Changes

• pnpm rebuild should not fail when node-linker is set to hoisted and there are skipped optional dependencies #​6553.
• Expanded missing command error, including 'did you mean' #​6492.
• Normalize current working directory on Windows #​6524.
• Build projects in a workspace in correct order #​6568.

Our Gold Sponsors

Our Silver Sponsors

v7.32.4

Compare Source

Patch Changes

• pnpm link -g <pkg-name> should not modify the package.json file #​4341.
• Node.js range specified through the engines field should match prerelease versions #​6509.
• pnpm publish --otp should work #​6514.

Our Gold Sponsors

Our Silver Sponsors

v7.32.3

Compare Source

Patch Changes

• Link the bin files of local workspace dependencies, when node-linker is set to hoisted 6486.
• Show cyclic workspace dependency details #​5059.

Our Gold Sponsors

Our Silver Sponsors

v7.32.2

Compare Source

Patch Changes

• Patch node-fetch to fix an error that happens on Node.js 20 #​6424.

Our Gold Sponsors

Our Silver Sponsors

v7.32.1

Compare Source

Patch Changes

• Warn user when publishConfig.directory of an injected workspace dependency does not exist #​6396.
• Use hard links to link the node executable on Windows machines #​4315.

Our Gold Sponsors

Our Silver Sponsors

v7.32.0

Compare Source

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

• pnpm config get <key> returns empty when the value is a boolean
• Don't print an info message about linked dependencies if they are real linked dependencies specified via the link: protocol in package.json.
• Add -g to mismatch registries error info when original command has -g option #​6224.

Our Gold Sponsors

Our Silver Sponsors

v7.31.0

Compare Source

Minor Changes

• Add ignore-workspace-cycles to silence workspace cycle warning #​6308.

Patch Changes

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

Our Gold Sponsors

Our Silver Sponsors

pnpm/action-setup (pnpm/action-setup)

v2.4.0

Compare Source

Add ability to install standalone binary (https://github.com/pnpm/action-setup/pull/92).

v2.3.0

Compare Source

• feat: specifying path to non-root package.json file (https://github.com/pnpm/action-setup/pull/88).
• docs: improve.

vitest-dev/vitest (vitest)

v0.34.1

Compare Source

   🐞 Bug Fixes

• Pass --experimental-vm-worker-memory-limit to tinypool  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/3856 (3c67a)

    View changes on GitHub

v0.34.0

Compare Source

   🚨 Breaking Changes

• Transform mode affects only test files, not regular files  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3491 (9608b)
  • transformMode is now moved to server.transformMode. This option is highly discouraged to use. If you need to change the transform mode, use the new option testTransformMode instead to control the mode based on the running test, not the current file path. By default, tests with jsdom or happy-dom use web transform mode, and tests using node or edge environment use ssr mode. If you have a custom environment, it should provide transformMode property.
• Disable coverage.reportOnFailure by default  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/3615 (0c6f6)
• Remove @vitest/coverage-c8 package  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/3614 (a90d6)
  • @vitest/coverage-c8 is no longer supported. Please, use @vitest/coverage-v8 instead.
• Support running tests using VM context  -  by @​sheremet-va and @​dammy001 in [https://github.com/feat!: support running tests using VM context vitest-dev/vitest#3203](https://togithub.com/vitest-dev/vitest/issu

---

Configuration

📅 Schedule: Branch creation - "after 6pm on sunday" in timezone Asia/Shanghai, 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

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