Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 21, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@iconify-json/lucide ^1.2.32 -> ^1.2.34 age adoption passing confidence
@iconify-json/simple-icons ^1.2.29 -> ^1.2.30 age adoption passing confidence
@iconify-json/vscode-icons ^1.2.16 -> ^1.2.18 age adoption passing confidence
@nuxt/eslint (source) ^1.2.0 -> ^1.3.0 age adoption passing confidence
@nuxt/ui-pro (source) ^3.0.1 -> ^3.0.2 age adoption passing confidence
eslint (source) ^9.22.0 -> ^9.23.0 age adoption passing confidence
nuxt-llms 0.1.0 -> 0.1.2 age adoption passing confidence
nuxt-og-image (source) ^5.0.5 -> ^5.1.1 age adoption passing confidence
pnpm (source) 10.6.5 -> 10.7.0 age adoption passing confidence

Release Notes

nuxt/eslint (@​nuxt/eslint)

v1.3.0

Compare Source

   🚀 Features
    View changes on GitHub
eslint/eslint (eslint)

v9.23.0

Compare Source

nuxtlabs/nuxt-llms (nuxt-llms)

v0.1.2

Compare Source

compare changes

🩹 Fixes
  • Omit description if undefined (#​11)
  • hooks: Check if any hooks are registered before logging the deprecation warning (#​10)
  • Hooks warning check (7d627f4)
🏡 Chore
❤️ Contributors

v0.1.1

Compare Source

compare changes

🩹 Fixes
🏡 Chore
❤️ Contributors
nuxt-modules/og-image (nuxt-og-image)

v5.1.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v5.1.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    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.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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 was generated by Mend Renovate. View the repository job log.

@cloudflare-workers-and-pages
Copy link

cloudflare-workers-and-pages bot commented Mar 21, 2025

Deploying docs-template-3erl with  Cloudflare Pages  Cloudflare Pages

Latest commit: 88ea500
Status: ✅  Deploy successful!
Preview URL: https://bcefcffa.docs-template-3erl.pages.dev
Branch Preview URL: https://renovate-main-all-minor-patc.docs-template-3erl.pages.dev

View logs

@renovate renovate bot changed the title chore(deps): update devdependency eslint to ^9.23.0 (main) chore(deps): update all non-major dependencies (main) Mar 22, 2025
@renovate renovate bot force-pushed the renovate/main-all-minor-patch branch 9 times, most recently from a3ce565 to 1ae35e7 Compare March 28, 2025 16:32
@renovate renovate bot force-pushed the renovate/main-all-minor-patch branch from 1ae35e7 to 0afa212 Compare March 31, 2025 02:31
@renovate renovate bot force-pushed the renovate/main-all-minor-patch branch from 0afa212 to 88ea500 Compare March 31, 2025 06:05
@benjamincanac benjamincanac merged commit 1e9b5b1 into main Mar 31, 2025
2 checks passed
@benjamincanac benjamincanac deleted the renovate/main-all-minor-patch branch March 31, 2025 08:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants