Skip to content

chore(deps): update dependency npm-run-all2 to v8#1990

Merged
darkmatter18 merged 1 commit into
masterfrom
renovate/npm-run-all2-8.x
Jun 2, 2025
Merged

chore(deps): update dependency npm-run-all2 to v8#1990
darkmatter18 merged 1 commit into
masterfrom
renovate/npm-run-all2-8.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented May 27, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
npm-run-all2 7.0.2 -> 8.0.4 age adoption passing confidence

Release Notes

bcomnes/npm-run-all2 (npm-run-all2)

v8.0.4

Compare Source

Commits

v8.0.3

Compare Source

Commits
  • Merge pull request #​175 from bcomnes/revert-pico 75bb00e
  • Revert "replace minimatch with picomatch" 5d93a54

v8.0.2

Compare Source

Commits

v8.0.1

Compare Source

Commits
  • Merge pull request #​159 from bcomnes/dependabot/npm_and_yarn/minimatch-10.0.1 54af3ab
  • Upgrade: Bump minimatch from 9.0.5 to 10.0.1 f50ddf4
  • Merge pull request #​170 from bcomnes/fix-engine-range e43e670

v8.0.0

Compare Source

Commits
  • Breaking change: Raise engine floor to >= Node 20 b1b12f8
  • Merge pull request #​169 from bcomnes/node-20-or-greater bb27458

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.

🔕 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
Copy link
Copy Markdown
Contributor Author

renovate Bot commented May 27, 2025

⚠️ 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 warn Unknown env config "store". This will stop working in the next major version of npm.
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: react-auth-kit@2.12.7
npm warn Found: typedoc@0.27.6
npm warn node_modules/typedoc
npm warn   dev typedoc@"0.28.5" from the root project
npm warn   1 more (typedoc-plugin-markdown)
npm warn
npm warn Could not resolve dependency:
npm warn peer typedoc@"0.27.x" from typedoc-plugin-markdown@4.4.1
npm warn node_modules/typedoc-plugin-markdown
npm warn   dev typedoc-plugin-markdown@"^4.0.0" from the root project
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @auth-kit/next@3.1.3
npm error Found: react@19.0.0
npm error node_modules/react
npm error   dev react@"19.0.0" from @auth-kit/next@3.1.3
npm error   packages/next
npm error     @auth-kit/next@3.1.3
npm error     node_modules/@auth-kit/next
npm error       workspace packages/next from the root project
npm error   peer react@"^18.2.0 || 19.0.0-rc-de68d2f4-20241204 || ^19.0.0" from next@15.2.4
npm error   node_modules/next
npm error     dev next@"15.2.4" from @auth-kit/next@3.1.3
npm error     packages/next
npm error       @auth-kit/next@3.1.3
npm error       node_modules/@auth-kit/next
npm error         workspace packages/next from the root project
npm error
npm error Could not resolve dependency:
npm error peer react@"^19.1.0" from react-dom@19.1.0
npm error node_modules/react-dom
npm error   peer react-dom@"^18.2.0 || 19.0.0-rc-de68d2f4-20241204 || ^19.0.0" from next@15.2.4
npm error   node_modules/next
npm error     dev next@"15.2.4" from @auth-kit/next@3.1.3
npm error     packages/next
npm error       @auth-kit/next@3.1.3
npm error       node_modules/@auth-kit/next
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-05-27T09_10_35_696Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-05-27T09_10_35_696Z-debug-0.log

@renovate renovate Bot force-pushed the renovate/npm-run-all2-8.x branch from aadb7a7 to f28477f Compare May 27, 2025 09:10
@darkmatter18 darkmatter18 merged commit dc9a9f5 into master Jun 2, 2025
7 of 26 checks passed
@renovate renovate Bot deleted the renovate/npm-run-all2-8.x branch June 2, 2025 10:34
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