Skip to content

Update all non-major dependencies (main) #79

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 5, 2025

This PR contains the following updates:

Package Change Age Confidence
@iconify-json/lucide ^1.2.34 -> ^1.2.57 age confidence
@iconify-json/simple-icons ^1.2.30 -> ^1.2.44 age confidence
@iconify-json/vscode-icons ^1.2.18 -> ^1.2.23 age confidence
@nuxt/content (source) ^3.4.0 -> ^3.6.3 age confidence
@nuxt/eslint (source) ^1.3.0 -> ^1.7.0 age confidence
@nuxt/ui-pro (source) ^3.0.2 -> ^3.2.0 age confidence
@nuxtjs/robots (source) 5.2.10 -> 5.4.0 age confidence
@nuxtjs/sitemap 7.2.10 -> 7.4.3 age confidence
eslint (source) ^9.23.0 -> ^9.31.0 age confidence
nuxt-gtag 3.0.2 -> 3.0.3 age confidence
nuxt-llms 0.1.2 -> 0.1.3 age confidence
nuxt-og-image (source) ^5.1.1 -> ^5.1.9 age confidence
pnpm (source) 10.7.0 -> 10.13.1 age confidence
typescript (source) ^5.8.2 -> ^5.8.3 age confidence

Release Notes

nuxt/content (@​nuxt/content)

v3.6.3

Compare Source

Bug Fixes

v3.6.2

Compare Source

Features
  • schema: set navigation.icon of page as icon for preview (eff825d)
Bug Fixes

v3.6.1

Compare Source

Features
Bug Fixes

v3.6.0

Compare Source

Features
  • add findPageBreadcrumb, findPageChildren and findPageSiblings utils (#​3393) (c74ec44)
  • parser: allow extra transformers to provide components used (#​3355) (baff541)
  • source: do not watch for excluded files (2ee1149)
  • toggle content heading extraction (#​3400) (f01256a)
  • use json schema instead of zod for internal routines (#​3347) (3f2ff74)
Bug Fixes
nuxt/eslint (@​nuxt/eslint)

v1.7.0

Compare Source

   🚀 Features
    View changes on GitHub

v1.6.0

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v1.5.2

Compare Source

   🚀 Features
    View changes on GitHub

v1.5.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v1.5.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v1.4.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v1.4.0

Compare Source

   🚀 Features
    View changes on GitHub

v1.3.1

Compare Source

No significant changes

    View changes on GitHub
nuxt/ui-pro (@​nuxt/ui-pro)

v3.2.0

Compare Source

v3.1.3

Compare Source

v3.1.2

Compare Source

v3.1.1

Compare Source

nuxt-modules/robots (@​nuxtjs/robots)

v5.4.0

Compare Source

   🚀 Features
    View changes on GitHub

v5.3.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v5.2.11

Compare Source

   🐞 Bug Fixes
    View changes on GitHub
nuxt-modules/sitemap (@​nuxtjs/sitemap)

v7.4.3

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v7.4.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v7.4.1

Compare Source

   🏎 Performance
    View changes on GitHub

v7.4.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v7.3.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v7.3.0

Compare Source

⚠️ This release introduces several features, performance improvements and bug fixes, it's recommended to test your sitemap after upgrading.

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub
eslint/eslint (eslint)

v9.31.0

Compare Source

v9.30.1

Compare Source

v9.30.0

Compare Source

v9.29.0

Compare Source

v9.28.0

Compare Source

v9.27.0

Compare Source

v9.26.0

Compare Source

johannschopplich/nuxt-gtag (nuxt-gtag)

v3.0.3

Compare Source

   🐞 Bug Fixes
    View changes on GitHub
nuxtlabs/nuxt-llms (nuxt-llms)

v0.1.3

Compare Source

compare changes

🩹 Fixes
  • Using custom description provided within the llms:generate hook (#​16)
🏡 Chore
❤️ Contributors
nuxt-modules/og-image (nuxt-og-image)

v5.1.9

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v5.1.8

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v5.1.7

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v5.1.6

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v5.1.5

Compare Source

   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v5.1.4

Compare Source

   🐞 Bug Fixes
    View changes on GitHub
pnpm/pnpm (pnpm)

v10.13.1

Compare Source

Patch Changes
  • Run user defined pnpmfiles after pnpmfiles of plugins.

v10.13.0

Compare Source

Minor Changes
  • Added the possibility to load multiple pnpmfiles. The pnpmfile setting can now accept a list of pnpmfile locations #​9702.

  • pnpm will now automatically load the pnpmfile.cjs file from any config dependency named @pnpm/plugin-* or pnpm-plugin-* #​9729.

    The order in which config dependencies are initialized should not matter — they are initialized in alphabetical order. If a specific order is needed, the paths to the pnpmfile.cjs files in the config dependencies can be explicitly listed using the pnpmfile setting in pnpm-workspace.yaml.

Patch Changes
  • When patching dependencies installed via pkg.pr.new, treat them as Git tarball URLs #​9694.
  • Prevent conflicts between local projects' config and the global config in dangerouslyAllowAllBuilds, onlyBuiltDependencies, onlyBuiltDependenciesFile, and neverBuiltDependencies #​9628.
  • Sort keys in pnpm-workspace.yaml with deep #​9701.
  • The pnpm rebuild command should not add pkgs included in ignoredBuiltDependencies to ignoredBuilds in node_modules/.modules.yaml #​9338.
  • Replaced shell-quote with shlex for quoting command arguments #​9381.

v10.12.4

Compare Source

Patch Changes

v10.12.3

Compare Source

Patch Changes
  • Restore hoisting of optional peer dependencies when installing with an outdated lockfile.
    Regression introduced in v10.12.2 by #​9648; resolves #​9685.

v10.12.2

Compare Source

Patch Changes
  • Fixed hoisting with enableGlobalVirtualStore set to true #​9648.
  • Fix the --help and -h flags not working as expected for the pnpm create command.
  • The dependency package path output by the pnpm licenses list --json command is incorrect.
  • Fix a bug in which pnpm deploy fails due to overridden dependencies having peer dependencies causing ERR_PNPM_OUTDATED_LOCKFILE #​9595.

v10.12.1

Minor Changes
  • Experimental. Added support for global virtual stores. When enabled, node_modules contains only symlinks to a central virtual store, rather to node_modules/.pnpm. By default, this central store is located at <store-path>/links (you can find the store path by running pnpm store path).

    In the central virtual store, each package is hard linked into a directory whose name is the hash of its dependency graph. This allows multiple projects on the system to symlink shared dependencies from this central location, significantly improving installation speed when a warm cache is available.

    This is conceptually similar to how NixOS manages packages, using dependency graph hashes to create isolated and reusable package directories.

    To enable the global virtual store, set enableGlobalVirtualStore: true in your root pnpm-workspace.yaml, or globally via:

    pnpm config -g set enable-global-virtual-store true

    NOTE: In CI environments, where caches are typically cold, this setting may slow down installation. pnpm automatically disables the global virtual store when running in CI.

    Related PR: #​8190

  • The pnpm update command now supports updating catalog: protocol dependencies and writes new specifiers to pnpm-workspace.yaml.
  • Added two new CLI options (--save-catalog and --save-catalog-name=<name>) to pnpm add to save new dependencies as catalog entries. catalog: or catalog:<name> will be added to package.json and the package specifier will be added to the catalogs or catalog[<name>] object in pnpm-workspace.yaml #​9425.
  • Semi-breaking. The keys used for side-effects caches have changed. If you have a side-effects cache generated by a previous version of pnpm, the new version will not use it and will create a new cache instead #​9605.
  • Added a new setting called ci for explicitly telling pnpm if the current environment is a CI or not.
Patch Changes
  • Sort versions printed by pnpm patch using semantic versioning rules.
  • Improve the way the error message displays mismatched specifiers. Show differences instead of 2 whole objects #​9598.
  • Revert #​9574 to fix a regression #​9596.

v10.11.1

Compare Source

Patch Changes
  • Fix an issue in which pnpm deploy --legacy creates unexpected directories when the root package.json has a workspace package as a peer dependency #​9550.
  • Dependencies specified via a URL that redirects will only be locked to the target if it is immutable, fixing a regression when installing from GitHub releases. (#​9531)
  • Installation should not exit with an error if strictPeerDependencies is true but all issues are ignored by peerDependencyRules #​9505.
  • Use pnpm_config_ env variables instead of npm_config_ #​9571.
  • Fix a regression (in v10.9.0) causing the --lockfile-only flag on pnpm update to produce a different pnpm-lock.yaml than an update without the flag.
  • Let pnpm deploy work in repos with overrides when inject-workspace-packages=true #​9283.
  • Fixed the problem of path loss caused by parsing URL address. Fixes a regression shipped in pnpm v10.11 via #​9502.
  • pnpm -r --silent run should not print out section #​9563.

v10.11.0

Compare Source

Minor Changes
  • A new setting added for pnpm init to create a package.json with type=module, when init-type is module. Works as a flag for the init command too #​9463.

  • Added support for Nushell to pnpm setup #​6476.

  • Added two new flags to the pnpm audit command, --ignore and --ignore-unfixable #​8474.

    Ignore all vulnerabilities that have no solution:

    > pnpm audit --ignore-unfixable

    Provide a list of CVE's to ignore those specifically, even if they have a resolution.

    > pnpm audit --ignore=CVE-2021-1234 --ignore=CVE-2021-5678
  • Added support for recursively running pack in every project of a workspace #​4351.

    Now you can run pnpm -r pack to pack all packages in the workspace.

Patch Changes
  • pnpm version management should work, when dangerouslyAllowAllBuilds is set to true #​9472.
  • pnpm link should work from inside a workspace #​9506.
  • Set the default workspaceConcurrency to Math.min(os.availableParallelism(), 4) #​9493.
  • Installation should not exit with an error if strictPeerDependencies is true but all issues are ignored by peerDependencyRules #​9505.
  • Read updateConfig from pnpm-workspace.yaml #​9500.
  • Add support for recursive pack
  • Remove url.parse usage to fix warning on Node.js 24 #​9492.
  • pnpm run should be able to run commands from the workspace root, if ignoreScripts is set tot true #​4858.

v10.10.0

Compare Source

Minor Changes
  • Allow loading the preResolution, importPackage, and fetchers hooks from local pnpmfile.
Patch Changes
  • Fix cd command, when shellEmulator is true #​7838.
  • Sort keys in pnpm-workspace.yaml #​9453.
  • Pass the npm_package_json environment variable to the executed scripts #​9452.
  • Fixed a mistake in the description of the --reporter=silent option.

v10.9.0

Compare Source

Minor Changes
  • Added support for installing JSR packages. You can now install JSR packages using the following syntax:

    pnpm add jsr:<pkg_name>
    

    or with a version range:

    pnpm add jsr:<pkg_name>@&#8203;<range>
    

    For example, running:

    pnpm add jsr:@&#8203;foo/bar
    

    will add the following entry to your package.json:

    {
      "dependencies": {
        "@&#8203;foo/bar": "jsr:^0.1.2"
      }
    }

    When publishing, this entry will be transformed into a format compatible with npm, older versions of Yarn, and previous pnpm versions:

    {
      "dependencies": {
        "@&#8203;foo/bar": "npm:@&#8203;jsr/foo__bar@^0.1.2"
      }
    }

    Related issue: #​8941.

    Note: The @jsr scope defaults to https://npm.jsr.io/ if the @jsr:registry setting is not defined.

  • Added a new setting, dangerouslyAllowAllBuilds, for automatically running any scripts of dependencies without the need to approve any builds. It was already possible to allow all builds by adding this to pnpm-workspace.yaml:

    neverBuiltDependencies: []

    dangerouslyAllowAllBuilds has the same effect but also allows to be set globally via:

    pnpm config set dangerouslyAllowAllBuilds true
    

    It can also be set when running a command:

    pnpm install --dangerously-allow-all-builds
    
Patch Changes
  • Fix a false negative in verifyDepsBeforeRun when nodeLinker is hoisted and there is a workspace package without dependencies and node_modules directory #​9424.
  • Explicitly drop verifyDepsBeforeRun support for nodeLinker: pnp. Combining verifyDepsBeforeRun and nodeLinker: pnp will now print a warning.

v10.8.1

Compare Source

Patch Changes
  • Removed bright white highlighting, which didn't look good on some light themes #​9389.
  • If there is no pnpm related configuration in package.json, onlyBuiltDependencies will be written to pnpm-workspace.yaml file #​9404.

v10.8.0

Compare Source

Minor Changes
  • Experimental. A new hook is supported for updating configuration settings. The hook can be provided via .pnpmfile.cjs. For example:

    module.exports = {
      hooks: {
        updateConfig: (config) => ({
          ...config,
          nodeLinker: "hoisted",
        }),
      },
    };
  • Now you can use the pnpm add command with the --config flag to install new configurational dependencies #​9377.

Patch Changes
  • Do not hang indefinitely, when there is a glob that starts with !/ in pnpm-workspace.yaml. This fixes a regression introduced by #​9169.
  • pnpm audit --fix should update the overrides in pnpm-workspace.yaml.
  • pnpm link should update overrides in pnpm-workspace.yaml, not in package.json #​9365.

v10.7.1

Compare Source

Patch Changes
  • pnpm config set should convert the settings to their correct type before adding them to pnpm-workspace.yaml #​9355.
  • pnpm config get should read auth related settings via npm CLI #​9345.
  • Replace leading ~/ in a path in .npmrc with the home directory #​9217.

Configuration

📅 Schedule: Branch creation - "on Monday" (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.

👻 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

coderabbitai bot commented May 5, 2025

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Join our Discord community for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@renovate renovate bot force-pushed the renovate/main-all-minor-patch branch 3 times, most recently from e8e50d3 to bc9318f Compare May 11, 2025 14:05
@renovate renovate bot force-pushed the renovate/main-all-minor-patch branch 7 times, most recently from 2687fad to 402a3ff Compare May 16, 2025 22:46
@renovate renovate bot force-pushed the renovate/main-all-minor-patch branch 2 times, most recently from 8fc6971 to cdcecb9 Compare May 26, 2025 19:20
@renovate renovate bot force-pushed the renovate/main-all-minor-patch branch 7 times, most recently from 7b8585d to aaaa11e Compare June 3, 2025 04:44
@renovate renovate bot force-pushed the renovate/main-all-minor-patch branch 6 times, most recently from 7b03f45 to 899564b Compare June 8, 2025 22:57
@renovate renovate bot force-pushed the renovate/main-all-minor-patch branch 4 times, most recently from 8efecf8 to cf7c6e2 Compare June 14, 2025 05:39
@renovate renovate bot force-pushed the renovate/main-all-minor-patch branch 8 times, most recently from e0d76fd to 8c772cf Compare June 27, 2025 05:33
@renovate renovate bot force-pushed the renovate/main-all-minor-patch branch 11 times, most recently from d30781a to 4449430 Compare July 4, 2025 14:45
@renovate renovate bot force-pushed the renovate/main-all-minor-patch branch 6 times, most recently from bda7cf1 to 4af9456 Compare July 11, 2025 21:13
@renovate renovate bot force-pushed the renovate/main-all-minor-patch branch 3 times, most recently from 818529c to b3c9789 Compare July 20, 2025 05:47
@renovate renovate bot force-pushed the renovate/main-all-minor-patch branch from b3c9789 to c2ba7d5 Compare July 22, 2025 10:53
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.

0 participants