[renovate]

This PR contains the following updates:

Package	Type	Update	Change
npm-run-all → npm-run-all2	devDependencies	replacement	^4.1.5 → ^5.0.0

This is a special PR that replaces npm-run-all with the community suggested minimal stable replacement version.

---

Configuration

📅 Schedule: (UTC)

• 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: resource-hub-by-revrebel@0.1.0
npm ERR! Found: react@18.3.1
npm ERR! node_modules/react
npm ERR!   react@"^18.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16" from netlify-cms-widget-inline-select@1.5.0
npm ERR! node_modules/netlify-cms-widget-inline-select
npm ERR!   netlify-cms-widget-inline-select@"^1.5.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2026-10-26T23_59_35_396Z-debug-0.log

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[netlify]

❌ Deploy Preview for resouce-hub failed.

Name	Link
🔨 Latest commit	39c4529
🔍 Latest deploy log	https://app.netlify.com/projects/resouce-hub/deploys/6adfe9c492d6dbd73395e636

[llamapreview]

LlamaPReview — Verification needed

Whether the head pnpm-lock.yaml resolves npm-run-all2, drops npm-run-all, and installs cleanly with a frozen lockfile. A consistent lockfile that installs cleanly makes the change supported and mergeable; an inconsistent lockfile or retained old pin makes it contradicted and unmergeable.

Exact-head CI remains unresolved (5 failed); no CI-dependent merge-safety claim is made.

Owner action: Read the head pnpm-lock.yaml or run pnpm install --lockfile-only/pnpm install --frozen-lockfile against the PR head to confirm npm-run-all2 resolves and npm-run-all is absent.

2 further items in details.

Review details and evidence

Material unknowns

• Whether the head pnpm-lock.yaml resolves npm-run-all2, drops npm-run-all, and installs cleanly with a frozen lockfile. A consistent lockfile that installs cleanly makes the change supported and mergeable; an inconsistent lockfile or retained old pin makes it contradicted and unmergeable.
• Whether the Netlify deploy-preview failure at the same head is caused by this dependency swap/lockfile or is independent of the PR. If caused by the change, it is PR-related and materially defeats the objective; if independent, it does not block merge.
  • Check: Obtain the Netlify deploy log to determine the failing step and whether this PR caused it.
• Why the renovate/artifacts step failed at head. Consistent with the lockfile being the weak spot, but the mechanism is unobserved; it remains an indicator rather than a diagnosis.
  • Check: Inspect the failing renovate/artifacts step output to see whether the lockfile regeneration failed.

LlamaPReview checks

• Reviewed changed regions in pnpm-lock.yaml.
• Reviewed changed regions in package.json.

---

LlamaPReview is an open-source pull request reviewer. Read the exact code that produced this review.