Skip to content

chore(deps): update all non-major dependencies #67

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

Merged
merged 1 commit into from
Mar 31, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 31, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@sxzz/eslint-config ^6.1.0 -> ^6.1.1 age adoption passing confidence
@types/node (source) ^22.13.13 -> ^22.13.14 age adoption passing confidence
pnpm (source) 10.6.5 -> 10.7.0 age adoption passing confidence
tsdown ^0.6.9 -> ^0.6.10 age adoption passing confidence
vite (source) ^6.2.3 -> ^6.2.4 age adoption passing confidence
vitest (source) ^3.0.9 -> ^3.1.1 age adoption passing confidence

Release Notes

sxzz/eslint-config (@​sxzz/eslint-config)

v6.1.1

Compare Source

No significant changes

    View changes on GitHub
pnpm/pnpm (pnpm)

v10.7.0

Compare Source

Minor Changes
  • pnpm config get and list also show settings set in pnpm-workspace.yaml files #​9316.

  • It should be possible to use env variables in pnpm-workspace.yaml setting names and value.

  • Add an ability to patch dependencies by version ranges. Exact versions override version ranges, which in turn override name-only patches. Version range * is the same as name-only, except that patch application failure will not be ignored.

    For example:

    patchedDependencies:
      foo: patches/foo-1.patch
      foo@^2.0.0: patches/foo-2.patch
      [email protected]: patches/foo-3.patch

    The above configuration would apply patches/foo-3.patch to [email protected], patches/foo-2.patch to all foo versions which satisfy ^2.0.0 except 2.1.0, and patches/foo-1.patch to the remaining foo versions.

    [!WARNING]
    The version ranges should not overlap. If you want to specialize a sub range, make sure to exclude it from the other keys. For example:

    # pnpm-workspace.yaml
    patchedDependencies:
      # the specialized sub range
      '[email protected]': patches/foo.2.2.0-2.8.0.patch
      # the more general patch, excluding the sub range above
      'foo@>=2.0.0 <2.2.0 || >2.8.0': 'patches/foo.gte2.patch

    In most cases, however, it's sufficient to just define an exact version to override the range.

  • pnpm config set --location=project saves the setting to a pnpm-workspace.yaml file if no .npmrc file is present in the directory #​9316.

  • Rename pnpm.allowNonAppliedPatches to pnpm.allowUnusedPatches. The old name is still supported but it would print a deprecation warning message.

  • Add pnpm.ignorePatchFailures to manage whether pnpm would ignore patch application failures.

    If ignorePatchFailures is not set, pnpm would throw an error when patches with exact versions or version ranges fail to apply, and it would ignore failures from name-only patches.

    If ignorePatchFailures is explicitly set to false, pnpm would throw an error when any type of patch fails to apply.

    If ignorePatchFailures is explicitly set to true, pnpm would print a warning when any type of patch fails to apply.

Patch Changes
  • Remove dependency paths from audit output to prevent out-of-memory errors #​9280.
sxzz/tsdown (tsdown)

v0.6.10

Compare Source

No significant changes

    View changes on GitHub
vitejs/vite (vite)

v6.2.4

Compare Source

Please refer to CHANGELOG.md for details.

vitest-dev/vitest (vitest)

v3.1.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.1.0

Compare Source


Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

Copy link

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

Copy link

socket-security bot commented Mar 31, 2025

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

Package New capabilities Transitives Size Publisher
npm/@sxzz/[email protected]6.1.1 environment Transitive: filesystem, shell, unsafe +239 29.4 MB sxzz
npm/@types/[email protected]22.13.14 None +1 83.3 kB
npm/[email protected]0.6.10 Transitive: filesystem, shell +31 9.72 MB sxzz
npm/[email protected]6.2.4 None +7 3.27 MB
npm/[email protected]3.1.1 Transitive: environment, filesystem, shell, unsafe +31 1.16 MB

View full report↗︎

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from dfb3717 to 7d4c9f7 Compare March 31, 2025 07:28
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 7d4c9f7 to e76369a Compare March 31, 2025 11:41
@renovate renovate bot merged commit bf6fa03 into main Mar 31, 2025
9 checks passed
@renovate renovate bot deleted the renovate/all-minor-patch branch March 31, 2025 15:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants