Skip to content

chore(deps): update dependency yargs-parser to v22 - #1084

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/yargs-parser-22.x-lockfile
Open

chore(deps): update dependency yargs-parser to v22#1084
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/yargs-parser-22.x-lockfile

Conversation

@renovate

@renovate renovate Bot commented Aug 5, 2025

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
yargs-parser 20.2.922.0.0 age adoption passing confidence

Release Notes

yargs/yargs-parser (yargs-parser)

v22.0.0

Compare Source

⚠ BREAKING CHANGES
Features

v21.1.1

Compare Source

Bug Fixes

v21.1.0

Compare Source

Features
Bug Fixes
  • halt-at-non-option: prevent known args from being parsed when "unknown-options-as-args" is enabled (#​438) (c474bc1)
  • node version check now uses process.versions.node (#​450) (d07bcdb)
  • parse options ending with 3+ hyphens (#​434) (4f1060b)
21.0.1 (2022-02-27)
Bug Fixes

v21.0.1

Compare Source

Features
Bug Fixes
  • halt-at-non-option: prevent known args from being parsed when "unknown-options-as-args" is enabled (#​438) (c474bc1)
  • node version check now uses process.versions.node (#​450) (d07bcdb)
  • parse options ending with 3+ hyphens (#​434) (4f1060b)
21.0.1 (2022-02-27)
Bug Fixes

v21.0.0

Compare Source

Features
Bug Fixes
  • halt-at-non-option: prevent known args from being parsed when "unknown-options-as-args" is enabled (#​438) (c474bc1)
  • node version check now uses process.versions.node (#​450) (d07bcdb)
  • parse options ending with 3+ hyphens (#​434) (4f1060b)
21.0.1 (2022-02-27)
Bug Fixes

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • Between 12:00 AM and 03:59 AM (* 0-3 * * *)

🚦 Automerge: Disabled because a matching PR was automerged previously.

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 added the renovate label Aug 5, 2025
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Aug 5, 2025

Copy link
Copy Markdown

Deploying jonprentice-me with  Cloudflare Pages  Cloudflare Pages

Latest commit: d05b4a8
Status:🚫  Build failed.

View logs

@renovate
renovate Bot force-pushed the renovate/yargs-parser-22.x-lockfile branch 2 times, most recently from 1974d5b to 2a8601b Compare August 13, 2025 17:03
@renovate
renovate Bot force-pushed the renovate/yargs-parser-22.x-lockfile branch from 2a8601b to 9d448de Compare August 19, 2025 12:48
@renovate
renovate Bot force-pushed the renovate/yargs-parser-22.x-lockfile branch from 9d448de to 649767a Compare August 31, 2025 10:11
@renovate
renovate Bot force-pushed the renovate/yargs-parser-22.x-lockfile branch 2 times, most recently from 712cbc0 to 78ac030 Compare September 28, 2025 00:34
@renovate
renovate Bot force-pushed the renovate/yargs-parser-22.x-lockfile branch from 78ac030 to 32460c5 Compare October 22, 2025 15:49
@renovate
renovate Bot force-pushed the renovate/yargs-parser-22.x-lockfile branch from 32460c5 to 03c0678 Compare November 18, 2025 12:42
@renovate
renovate Bot force-pushed the renovate/yargs-parser-22.x-lockfile branch from 03c0678 to 119ddfd Compare December 3, 2025 14:48
@renovate
renovate Bot force-pushed the renovate/yargs-parser-22.x-lockfile branch from 119ddfd to 00f4179 Compare December 31, 2025 17:11
@renovate
renovate Bot force-pushed the renovate/yargs-parser-22.x-lockfile branch 2 times, most recently from 98b1f99 to 59bc9a8 Compare January 19, 2026 18:13
@renovate
renovate Bot force-pushed the renovate/yargs-parser-22.x-lockfile branch 2 times, most recently from b3724f5 to bad7794 Compare February 9, 2026 05:12
@renovate
renovate Bot force-pushed the renovate/yargs-parser-22.x-lockfile branch 3 times, most recently from 0645a1d to 98261c9 Compare February 17, 2026 20:53
@renovate
renovate Bot force-pushed the renovate/yargs-parser-22.x-lockfile branch from 98261c9 to 8861329 Compare March 5, 2026 14:40
@renovate
renovate Bot force-pushed the renovate/yargs-parser-22.x-lockfile branch from 8861329 to 452ad76 Compare March 13, 2026 19:10
@renovate
renovate Bot force-pushed the renovate/yargs-parser-22.x-lockfile branch 2 times, most recently from 201d6e1 to cb46d1b Compare March 27, 2026 12:35
@renovate
renovate Bot force-pushed the renovate/yargs-parser-22.x-lockfile branch from cb46d1b to e3b6697 Compare April 1, 2026 18:48
@codacy-production

codacy-production Bot commented Apr 1, 2026

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric Results
Complexity 0
Duplication 0

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

@renovate
renovate Bot force-pushed the renovate/yargs-parser-22.x-lockfile branch 2 times, most recently from 1f8a8f6 to fbc6a44 Compare April 13, 2026 01:42
@renovate
renovate Bot force-pushed the renovate/yargs-parser-22.x-lockfile branch from fbc6a44 to 2a89328 Compare April 29, 2026 12:14
@renovate
renovate Bot force-pushed the renovate/yargs-parser-22.x-lockfile branch 2 times, most recently from 179af73 to 44f113d Compare May 18, 2026 04:28
@renovate
renovate Bot force-pushed the renovate/yargs-parser-22.x-lockfile branch from 44f113d to eebd60e Compare May 18, 2026 09:55
@renovate
renovate Bot force-pushed the renovate/yargs-parser-22.x-lockfile branch from eebd60e to e4627ca Compare May 28, 2026 17:59
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate
renovate Bot force-pushed the renovate/yargs-parser-22.x-lockfile branch from e4627ca to d05b4a8 Compare June 12, 2026 13:04
@renovate

renovate Bot commented Jul 12, 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: frontend/package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: jonprentice.me@0.1.0
npm error Found: @babel/eslint-parser@7.29.7
npm error node_modules/@babel/eslint-parser
npm error   dev @babel/eslint-parser@"8.0.1" from the root project
npm error
npm error Could not resolve dependency:
npm error dev @babel/eslint-parser@"8.0.1" from the root project
npm error
npm error Conflicting peer dependency: @babel/core@8.0.1
npm error node_modules/@babel/core
npm error   peer @babel/core@"^8.0.0" from @babel/eslint-parser@8.0.1
npm error   node_modules/@babel/eslint-parser
npm error     dev @babel/eslint-parser@"8.0.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps 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/2026-07-30T01_27_41_858Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-07-30T01_27_41_858Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants