Skip to content

chore(deps): update dependency argparse to v3 - #34

Open
renovate-appwrite[bot] wants to merge 1 commit into
mainfrom
renovate/argparse-3.x
Open

renovate-appwrite[bot] wants to merge 1 commit into
mainfrom
renovate/argparse-3.x

Conversation

@renovate-appwrite

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
argparse ^2.0.1 → ^3.0.0 age confidence

Release Notes

nodeca/argparse (argparse)

v3.0.4

Compare Source

Fixed
  • Kept UTF-16 surrogate pairs together when wrapping long help text, #​195.

v3.0.3

Compare Source

Security
  • Fixed ReDoS in int type conversion. Not critical for typical CLI use:
    an attacker with shell access can already run an infinite loop directly.

v3.0.2

Compare Source

Fixed
  • Aligned int and float conversion with Python: fixed negative zero for
    integers and accepted string formats for floats, #​191.
  • Fixed action: 'extend' to iterate over values and reject non-iterable values
    as in Python, including splitting scalar strings into characters, #​190.

v3.0.1

Compare Source

Fixed
  • Adjusted attribution to PSF-2.0 (not a license change), #​188.

v3.0.0

Compare Source

Added
  • Colored help output, enabled automatically on supported terminals and
    configurable with the color option.
  • Suggestions for mistyped choices and subcommands via suggest_on_error.
  • Deprecation warnings for arguments and subcommands marked with deprecated.
  • Built-in TypeScript declarations.
Changed
  • Updated the Python argparse port from 3.9.0 to 3.14.6.
Removed
  • Removed the deprecated v1 compatibility API and undocumented type: 'auto'.
    See the migration guide for replacements.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Only on Monday (* * * * 1)
  • 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 has been generated by Mend Renovate CLI.

@renovate-appwrite renovate-appwrite Bot added the dependencies Pull requests that update a dependency file label Nov 16, 2026
@appwrite

appwrite Bot commented Nov 16, 2026 •

Copy link
Copy Markdown

🟡 Tier B · Needs changes before merging

The stale lockfile makes npm ci fail, blocking the project's CI build.

The dependency override for js-yaml@3 is updated from argparse ^2.0.1 to ^3.0.0. The lockfile removes the previous top-level argparse entry.

Verdict New comments Fixed Still open
🛑 Changes requested 1 0 0
Finding Where
🟠 argparse lockfile entries are missing package-lock.json:5857
Fix with agent prompt
### Issue 1
package-lock.json:5857
**argparse lockfile entries are missing**

Running `npm ci` exits with `EUSAGE`: the lockfile has neither `argparse@3.0.4` for the new js-yaml@3 override nor `argparse@2.0.1`, which is still required by nested js-yaml@4. Since CI installs with `npm ci`, the build cannot run until both entries are present.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.
📂 Walkthrough · 2
File Change
package.json Updates the argparse override for js-yaml v3.
package-lock.json Removes the previous argparse lockfile entry.

Reviewed b2b9a16 · Details · Comment @appwrite review to re-run, or mention @appwrite with a question.

@appwrite appwrite Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🟡 Tier B · 1 blocking finding to address. Summary

Comment thread package-lock.json
"integrity": "sha512-8+9WqebbFzpX9OR+Wa6O29asIogeRMzcGtAINdpMHHyAg10f05aSFVBbcEqGf/PXw1EjAZ+q2/bEBg3DvurK3Q==",
"license": "Python-2.0"
},
"node_modules/asap": {

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

argparse lockfile entries are missing

Running npm ci exits with EUSAGE: the lockfile has neither argparse@3.0.4 for the new js-yaml@3 override nor argparse@2.0.1, which is still required by nested js-yaml@4. Since CI installs with npm ci, the build cannot run until both entries are present.

Prompt To Fix With AI
This is a comment left during a code review.
Path: package-lock.json
Line: 5857

Comment:
**argparse lockfile entries are missing**

Running `npm ci` exits with `EUSAGE`: the lockfile has neither `argparse@3.0.4` for the new js-yaml@3 override nor `argparse@2.0.1`, which is still required by nested js-yaml@4. Since CI installs with `npm ci`, the build cannot run until both entries are present.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

🟠 Major · bug · Reply if this doesn't apply.

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

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants