Skip to content

chore(deps): update dependency npm-run-all2 to v9#117

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-run-all2-9.x
Open

chore(deps): update dependency npm-run-all2 to v9#117
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-run-all2-9.x

Conversation

@renovate

@renovate renovate Bot commented May 26, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
npm-run-all2 8.0.49.0.1 age confidence

Reference


Release Notes

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

v9.0.1

Compare Source

Merged
  • fix: update help.js to include --node-run option details #230

v9.0.0

Compare Source

Merged
  • Add more colors based on terminal capabilities #222
  • Upgrade: Bump releasearoni from 0.1.14 to 0.2.0 #227
  • Breaking change: Glob patterns that match no tasks now succeed silently #226
  • Add -x / --node-run flag to bypass the package manager #225
  • Remove redundant build call from prepublishOnly #224
  • Whitelist files to include in npm package #199
  • Fix jsdoc types and use tsc for type safety checks #220
  • Upgrade: Bump codecov/codecov-action from 5 to 6 #215
  • Update SECURITY.md with new reporting process #201
  • Upgrade: Bump actions/checkout from 5 to 6 #200
  • Upgrade: Bump actions/setup-node from 5 to 6 #196
  • Upgrade: Bump github/codeql-action from 3 to 4 #195
  • Upgrade: Bump actions/setup-node from 4 to 5 #192
  • Upgrade: Bump actions/checkout from 4 to 5 #191
  • chore: fix typo in test #185
  • refactor: use optional chain for better readability #184
Fixed
  • Breaking change: Glob patterns that match no tasks now succeed silently (#​226) #149
  • Add -x / --node-run flag to use node --run instead of the package manager #155
  • docs: clarify glob pattern execution order guarantee #167
Commits
  • Add node-run smoke tests f4ac667
  • Implement releasaroni for the release process 6a2baff
  • Use shared publishing action b6a39a6

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "before 7am every weekday"
  • 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 renovate Bot requested a review from a team as a code owner May 26, 2026 03:05
@renovate renovate Bot requested review from a team and Bloomca and removed request for a team May 26, 2026 03:05
@renovate

renovate Bot commented May 26, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ 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 error code EBADENGINE
npm error engine Unsupported engine
npm error engine Not compatible with your version of node/npm: npm-run-all2@9.0.1
npm error notsup Not compatible with your version of node/npm: npm-run-all2@9.0.1
npm error notsup Required: {"node":"^22.22.2 || ^24.15.0 || >=26.0.0","npm":">= 10"}
npm error notsup Actual:   {"npm":"10.9.4","node":"v22.22.1"}
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-06-12T03_41_41_756Z-debug-0.log

@doistbot doistbot left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Thanks renovate[bot] for your contribution 😄 🙌. This updates npm-run-all2 to v9, and it's good to note that the breaking change regarding glob patterns won't negatively impact our existing scripts.

Few things worth tightening:

  • Regenerate and commit package-lock.json so it matches the updated package.json and doesn't break npm ci installs.

Share FeedbackReview Logs

Comment thread package.json Outdated
"husky": "9.1.7",
"lint-staged": "17.0.5",
"npm-run-all2": "8.0.4",
"npm-run-all2": "9.0.0",

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

P1 This change leaves package-lock.json out of sync: it still pins npm-run-all2 to 8.0.4. On this branch, npm ci will fail immediately because the lockfile no longer matches package.json. Regenerate and commit the lockfile with the version bump.

@renovate renovate Bot force-pushed the renovate/npm-run-all2-9.x branch 3 times, most recently from 150e4a0 to a1573c7 Compare May 29, 2026 07:29
@renovate renovate Bot force-pushed the renovate/npm-run-all2-9.x branch from a1573c7 to 28096d0 Compare June 8, 2026 03:32
@engfragui

Copy link
Copy Markdown
Contributor

@Bloomca Gentle reminder to look at this PR when you can 🙏

@renovate renovate Bot force-pushed the renovate/npm-run-all2-9.x branch from 28096d0 to 8e8983d Compare June 9, 2026 03:49
@renovate renovate Bot force-pushed the renovate/npm-run-all2-9.x branch from 8e8983d to a7f78ec Compare June 12, 2026 03:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants