Skip to content

refactor: Bump otpauth from 9.4.0 to 9.5.0#10423

Merged
mtrezza merged 1 commit intoparse-community:alphafrom
mtrezza:refactor/otpauth-9.5.0
Apr 10, 2026
Merged

refactor: Bump otpauth from 9.4.0 to 9.5.0#10423
mtrezza merged 1 commit intoparse-community:alphafrom
mtrezza:refactor/otpauth-9.5.0

Conversation

@mtrezza
Copy link
Copy Markdown
Member

@mtrezza mtrezza commented Apr 10, 2026

Closes #10403

Changes

Breaking Changes

  • None

Code Changes Required

  • None

Summary by CodeRabbit

  • Chores
    • Updated otpauth dependency to version 9.5.0 and corresponding transitive dependencies.
    • Updated Node.js engine requirement to version 20.19.0 or higher.

@parse-github-assistant
Copy link
Copy Markdown

🚀 Thanks for opening this pull request! We appreciate your effort in improving the project. Please let us know once your pull request is ready for review.

Tip

  • Keep pull requests small. Large PRs will be rejected. Break complex features into smaller, incremental PRs.
  • Use Test Driven Development. Write failing tests before implementing functionality. Ensure tests pass.
  • Group code into logical blocks. Add a short comment before each block to explain its purpose.
  • We offer conceptual guidance. Coding is up to you. PRs must be merge-ready for human review.
  • Our review focuses on concept, not quality. PRs with code issues will be rejected. Use an AI agent.
  • Human review time is precious. Avoid review ping-pong. Inspect and test your AI-generated code.

Note

Please respond to review comments from AI agents just like you would to comments from a human reviewer. Let the reviewer resolve their own comments, unless they have reviewed and accepted your commit, or agreed with your explanation for why the feedback was incorrect.

Caution

Pull requests must be written using an AI agent with human supervision. Pull requests written entirely by a human will likely be rejected, because of lower code quality, higher review effort and the higher risk of introducing bugs. Please note that AI review comments on this pull request alone do not satisfy this requirement. Our CI and AI review are safeguards, not development tools. If many issues are flagged, rethink your development approach. Invest more effort in planning and design rather than using review cycles to fix low-quality code.

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Apr 10, 2026

📝 Walkthrough

Walkthrough

Updated the otpauth npm package dependency from version 9.4.0 to 9.5.0 in package manifests and lockfile. This includes a transitive dependency update of @noble/hashes from 1.7.1 to 2.0.1 with a stricter minimum Node.js engine requirement (≥20.19.0).

Changes

Cohort / File(s) Summary
Dependency Version Bumps
package.json, package-lock.json
Updated otpauth from 9.4.0 to 9.5.0. Transitive update: @noble/hashes bumped from 1.7.1 to 2.0.1 with tightened Node.js engine requirement (>= 20.19.0).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 5 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name Status Explanation Resolution
Engage In Review Feedback ⚠️ Warning PR updates dependencies but fails to address review feedback regarding Node version incompatibility in workflow files. Update workflow files to Node 20.19.0+ or engage with reviewer regarding the incompatibility.
Linked Issues check ❓ Inconclusive The PR partially addresses the linked issue's objectives; it updates package manifests for otpauth 9.5.0 and dependency versions, but CI/workflow updates and test suite verification are not evident in the code changes provided. Confirm whether CI/workflow updates have been completed or if they are being handled separately; verify test suite execution confirms no breaking changes from @noble/hashes major version bump.
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title starts with the 'refactor:' prefix, which is allowed, and clearly describes the dependency version bump from 9.4.0 to 9.5.0.
Description check ✅ Passed The description follows the template structure, references the linked issue, explains the changes, and clarifies there are no breaking changes or code changes required.
Out of Scope Changes check ✅ Passed The code changes are limited to updating package.json and package-lock.json with otpauth 9.5.0 and related dependency versions, which are directly aligned with the linked issue objectives.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Security Check ✅ Passed This PR introduces only dependency version updates (otpauth 9.4.0→9.5.0 and @noble/hashes 1.7.1→2.0.1) with valid SHA512 integrity hashes from npm registry, no security vulnerabilities or malicious code.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 Checkov (3.2.513)
package.json

2026-04-10 19:55:22,125 [MainThread ] [ERROR] Template file not found: package.json
2026-04-10 19:55:22,132 [MainThread ] [ERROR] Template file not found: package.json
2026-04-10 19:55:22,135 [MainThread ] [ERROR] Template file not found: package.json
2026-04-10 19:55:22,197 [MainThread ] [ERROR] Failed to invoke function /usr/local/lib/python3.11/dist-packages/checkov/common/runners/object_runner. with package.json
Traceback (most recent call last):
File "/usr/local/lib/python3.11/dist-packages/checkov/common/parallelizer/parallel_runner.py", line 88, in func_wrapper
result = original_func(item)
^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/checkov/common/runners/object_runner.py", line 74, in
results = parallel_runner.run_function(lambda f: (f, self._parse_file(f)), files_to_load)
^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/checkov/ope

... [truncated 2547 characters] ...

ck__)
FileNotFoundError: [Errno 2] No such file or directory: 'package.json'
2026-04-10 19:55:22,234 [MainThread ] [ERROR] Exception traceback:
Traceback (most recent call last):
File "/usr/local/lib/python3.11/dist-packages/checkov/main.py", line 647, in run
self.scan_reports = runner_registry.run(
^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/checkov/common/runners/runner_registry.py", line 177, in run
for result in parallel_runner_results:
File "/usr/local/lib/python3.11/dist-packages/checkov/common/parallelizer/parallel_runner.py", line 118, in _run_function_multiprocess_fork
raise v.internal_exception.with_traceback(v.internal_exception.traceback)
FileNotFoundError: [Errno 2] No such file or directory: 'package.json'


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

coderabbitai[bot]
coderabbitai bot previously requested changes Apr 10, 2026
Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@package-lock.json`:
- Around line 3542-3547: The CI workflows release-manual-docs.yml and
release-prepare-monthly.yml pin Node 18.20.4 which is incompatible with the
transitive package `@noble/hashes` (engine >=20.19.0); update their GitHub Actions
setup-node steps to use Node 20.19.0 or a newer supported LTS (e.g., change
node-version / node-version-file/matrix entries in those workflows to "20.19.0"
or higher) so the actions run with a Node version that satisfies the declared
engines and prevents install failures.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 39e11093-6c9d-4d9f-98f1-605cfd09e8fa

📥 Commits

Reviewing files that changed from the base of the PR and between b55880d and d603857.

📒 Files selected for processing (2)
  • package-lock.json
  • package.json

Comment on lines +3542 to +3547
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/@noble/hashes/-/hashes-2.0.1.tgz",
"integrity": "sha512-XlOlEbQcE9fmuXxrVTXCTlG2nlRXa9Rj3rr5Ue/+tX+nmkgbX720YHh0VR3hBF9xDvwnb8D2shVGOwNx+ulArw==",
"license": "MIT",
"engines": {
"node": "^14.21.3 || >=16"
"node": ">= 20.19.0"
Copy link
Copy Markdown

@coderabbitai coderabbitai bot Apr 10, 2026

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== package.json engines =="
cat package.json | jq '.engines // "no engines field"'

echo
echo "== package-lock root package engines (if present) =="
cat package-lock.json | jq '.packages[""].engines // "no root lockfile engines field"'

echo
echo "== Node versions pinned in workflows =="
fd -i '.yml' .github/workflows -x sh -c '
  f="$1"
  echo "-- $f"
  rg -n "node-version|NODE_VERSION|setup-node|matrix" "$f" -C 2 || true
' sh {}

echo
echo "== Verify transitive engine floor in lockfile =="
cat package-lock.json | jq -r '.packages["node_modules/@noble/hashes"].engines.node'

Repository: parse-community/parse-server

Length of output: 8956


Update workflows to use Node versions compatible with declared engines.

The @noble/hashes@2.0.1 engine requirement (>= 20.19.0) aligns with the repo's declared minimum. However, release-manual-docs.yml and release-prepare-monthly.yml still pin Node 18.20.4, which is incompatible with both the declared engines (>=20.19.0) and the transitive dependency. Update these workflows to use a supported Node version (20.19.0 or newer) to prevent installation failures and ensure consistency with declared engines.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@package-lock.json` around lines 3542 - 3547, The CI workflows
release-manual-docs.yml and release-prepare-monthly.yml pin Node 18.20.4 which
is incompatible with the transitive package `@noble/hashes` (engine >=20.19.0);
update their GitHub Actions setup-node steps to use Node 20.19.0 or a newer
supported LTS (e.g., change node-version / node-version-file/matrix entries in
those workflows to "20.19.0" or higher) so the actions run with a Node version
that satisfies the declared engines and prevents install failures.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

The Node 18.20.4 pins in release-automated.yml and release-manual-docs.yml are pre-existing on the alpha branch and not introduced by this PR. This PR only modifies package.json and package-lock.json for the otpauth bump. The workflow Node version pins are a separate concern to be addressed in a dedicated PR.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

@mtrezza, understood — the workflow Node version pins are pre-existing and out of scope for this PR. Would you like me to open a follow-up GitHub issue to track updating the Node version pins in release-automated.yml and release-manual-docs.yml to a version compatible with @noble/hashes@2.0.1 (>= 20.19.0)?


🧠 Learnings used
Learnt from: mtrezza
Repo: parse-community/parse-server PR: 0
File: :0-0
Timestamp: 2025-12-02T08:00:20.138Z
Learning: For Parse Server 9 release (PR `#9938` and related), the parse/push-adapter dependency must be upgraded to version >= 8.0.0, not 7.0.0. Version 8.x drops support for Node 18.

Learnt from: mtrezza
Repo: parse-community/parse-server PR: 0
File: :0-0
Timestamp: 2025-12-02T08:00:08.440Z
Learning: For Parse Server 9 release preparation, the parse/push-adapter dependency should be upgraded to version >= 8.0.0, not 7.x, as version 8.x is required despite dropping Node 18 support (which aligns with Parse Server 9's removal of EOL Node versions).

Learnt from: mtrezza
Repo: parse-community/parse-server PR: 10082
File: package.json:3-3
Timestamp: 2026-02-28T15:22:57.025Z
Learning: In the parse-community/parse-server repository, manual changes to the npm package version in package.json should never be approved. The package version is managed and bumped automatically by semantic-release during the release workflow.

Learnt from: mtrezza
Repo: parse-community/parse-server PR: 0
File: :0-0
Timestamp: 2025-12-02T06:55:53.808Z
Learning: When reviewing Parse Server PRs that add or modify Parse Server options, always verify that changes are properly reflected in three files: src/Options/index.js (where changes originate), src/Options/Definitions.js, and src/Options/docs.js. The correct workflow is: make changes in index.js first, then run `npm run definitions` to automatically replicate the changes to Definitions.js and docs.js.

@mtrezza mtrezza dismissed coderabbitai[bot]’s stale review April 10, 2026 20:01

The flagged Node 18 workflow pins are pre-existing on the alpha branch and not introduced by this PR. The concern is valid but out-of-scope for this dependency bump.

@codecov
Copy link
Copy Markdown

codecov bot commented Apr 10, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.49%. Comparing base (b55880d) to head (d603857).
⚠️ Report is 1 commits behind head on alpha.

Additional details and impacted files
@@           Coverage Diff           @@
##            alpha   #10423   +/-   ##
=======================================
  Coverage   92.49%   92.49%           
=======================================
  Files         192      192           
  Lines       16786    16786           
  Branches      234      234           
=======================================
  Hits        15527    15527           
  Misses       1236     1236           
  Partials       23       23           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@mtrezza mtrezza merged commit 8b80e55 into parse-community:alpha Apr 10, 2026
24 checks passed
@mtrezza mtrezza deleted the refactor/otpauth-9.5.0 branch April 10, 2026 20:22
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