Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 27, 2025

This PR contains the following updates:

Package Change Age Confidence
@iconify-json/lucide ^1.2.71 -> ^1.2.72 age confidence
@iconify-json/simple-icons ^1.2.55 -> ^1.2.57 age confidence
@nuxt/content (source) ^3.7.1 -> ^3.8.0 age confidence
@nuxt/eslint (source) ^1.9.0 -> ^1.10.0 age confidence
eslint (source) ^9.38.0 -> ^9.39.1 age confidence
pnpm (source) 10.19.0 -> 10.20.0 age confidence
vue-tsc (source) ^3.1.2 -> ^3.1.3 age confidence

Release Notes

nuxt/content (@​nuxt/content)

v3.8.0

Compare Source

Features
Bug Fixes
  • extend inherited schema (dd054ea)
Performance Improvements
nuxt/eslint (@​nuxt/eslint)

v1.10.0

Compare Source

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

v9.39.1

Compare Source

v9.39.0

Compare Source

pnpm/pnpm (pnpm)

v10.20.0

Compare Source

Minor Changes
  • Support --all option in pnpm --help to list all commands #​8628.
Patch Changes
  • When the latest version doesn't satisfy the maturity requirement configured by minimumReleaseAge, pick the highest version that is mature enough, even if it has a different major version #​10100.
  • create command should not verify patch info.
  • Set managePackageManagerVersions to false, when switching to a different version of pnpm CLI, in order to avoid subsequent switches #​10063.
vuejs/language-tools (vue-tsc)

v3.1.3

Compare Source

Features
  • feat(typescript-plugin): allow triggering file references on <template> (#​5734) - Thanks to @​KazariEX!
Bug Fixes
  • fix(vscode): correct syntax highlight in template with lang="html" (#​5728) - Thanks to @​serkodev!
Other Changes
  • refactor(language-core): generate intrinsic elements variable into global types (#​5730) - Thanks to @​KazariEX!
  • refactor(typescript-plugin): remove go to definition trick for auto imported components (#​5733) - Thanks to @​KazariEX!

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.

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 25b8dc5 to 353d7c7 Compare October 29, 2025 00:27
@renovate renovate bot changed the title chore(deps): update dependency @iconify-json/simple-icons to ^1.2.56 chore(deps): update all non-major dependencies Oct 29, 2025
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 353d7c7 to f5d967b Compare October 29, 2025 18:44
Comment on lines +3859 to +3870
nuxt-component-meta@https://pkg.pr.new/nuxt-component-meta@e3eb2c4:
resolution: {tarball: https://pkg.pr.new/nuxt-component-meta@e3eb2c4}
version: 0.14.0
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The lock file is using an unreleased PR preview version of nuxt-component-meta instead of a published npm package, which will cause deployment and CI/CD failures.

View Details

Analysis

Lock file contains inaccessible pkg.pr.new dependency causing potential CI/CD failures

What fails: pnpm-lock.yaml references nuxt-component-meta@https://pkg.pr.new/nuxt-component-meta@e3eb2c4 which returns HTTP 404

How to reproduce:

curl -I "https://pkg.pr.new/nuxt-component-meta@e3eb2c4"
# Returns: HTTP/2 404

Result: Lock file contains 4 references to inaccessible URL that could fail in fresh CI/CD environments

Expected: Lock file should only reference stable, accessible package sources

Fix: Regenerating the lock file with rm pnpm-lock.yaml && pnpm install resolves to working dependencies and removes the problematic pkg.pr.new references entirely

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.

1 participant