Skip to content

refactor: Bump cross-env from 7.0.3 to 10.1.0#10579

Open
mtrezza wants to merge 1 commit into
parse-community:alphafrom
mtrezza:refactor/cross-env-10.1.0
Open

refactor: Bump cross-env from 7.0.3 to 10.1.0#10579
mtrezza wants to merge 1 commit into
parse-community:alphafrom
mtrezza:refactor/cross-env-10.1.0

Conversation

@mtrezza

@mtrezza mtrezza commented Jul 14, 2026

Copy link
Copy Markdown
Member

Closes #10435

Replaces the Dependabot PR with a manually verified upgrade of the cross-env devDependency, pinned to an exact version.

Changes

cross-env is a direct devDependency only (used in npm test, coverage, and benchmark scripts). This is a 3-major jump (7.x10.x); the intermediate majors were reviewed:

  • 8.0.0: Dropped support for old Node.js versions; raised the Node engine floor.
  • 9.0.0: Continued Node engine floor increase; internal packaging changes (ships compiled output from dist/).
  • 10.0.0: Node engine floor set to >=20. Added @epic-web/invariant as a runtime dependency and bumped the cross-spawn requirement to ^7.0.6.
  • 10.1.0: Latest patch/minor on the 10.x line.

The CLI surface (cross-env / cross-env-shell) is unchanged, so the existing npm scripts work without modification.

Breaking Changes

None affecting this repo. The only breaking change across v8/v9/v10 is the Node.js engine floor, now >=20. This repository already requires >=20.19.0 via engines.node, so the requirement is satisfied.

Code Changes Required

None. The upgrade is a drop-in replacement; no source or script changes are needed.

Summary by CodeRabbit

  • Chores
    • Updated the development tooling package cross-env to version 10.1.0.
    • Updated the lockfile to reflect the refreshed package metadata and dependencies.
    • The updated tooling now requires Node.js 20 or newer.

@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

coderabbitai Bot commented Jul 14, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

Updates cross-env from 7.0.3 to 10.1.0 in development dependencies and refreshes the lockfile with its metadata, @epic-web/invariant, updated cross-spawn requirements, distribution paths, and Node.js requirement.

Changes

cross-env dependency refresh

Layer / File(s) Summary
Update cross-env dependency resolution
package.json, package-lock.json
The development dependency and lockfile entries are updated to cross-env 10.1.0, including @epic-web/invariant, cross-spawn@^7.0.6, dist/bin/* paths, and a Node.js >=20 engine requirement.

Estimated code review effort: 2 (Simple) | ~10 minutes

Suggested reviewers: semantic-release-bot, dependabot[bot], moumouls, parseplatformorg, coratgerl


Caution

Pre-merge checks failed

Please resolve all errors before merging. Addressing warnings is optional.

  • Ignore

❌ Failed checks (2 errors)

Check name Status Explanation Resolution
Description check ❌ Error The description gives useful context, but it does not follow the required template headings and is missing the Tasks section. Add the required Issue, Approach, and Tasks sections, and include the checklist items from the repository template.
Engage In Review Feedback ❌ Error Only package.json and package-lock.json changed; the reviewed workflow still pins Node 18.20.4, so the feedback was not addressed. Update .github/workflows/release-manual-docs.yml to Node 20+ or discuss/retract the review comment before resolving it.
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title matches the dependency upgrade and follows the required refactor: prefix format.
Linked Issues check ✅ Passed The PR updates cross-env from 7.0.3 to 10.1.0 as requested by linked issue #10435.
Out of Scope Changes check ✅ Passed The changes are limited to package.json and package-lock.json for the cross-env version bump.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Security Check ✅ Passed Only unrelated cross-env.js malware showed up; cross-spawn is past CVE-2024-21538’s fixed range, and @epic-web/invariant has no advisories. citeturn11view0turn8view0turn11view1
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

@coderabbitai coderabbitai 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.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@package.json`:
- Line 85: Update the node-version setting in the manual docs workflow to Node
20 or newer, ensuring the job running npm ci and release_docs.sh uses the
repository’s supported toolchain. Keep the existing workflow behavior unchanged.
🪄 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: 82e3afa4-61ef-4943-a931-c31a44851869

📥 Commits

Reviewing files that changed from the base of the PR and between 6e87eb2 and 932b57b.

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

Comment thread package.json
"apollo-upload-client": "18.0.1",
"clean-jsdoc-theme": "4.3.0",
"cross-env": "7.0.3",
"cross-env": "10.1.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🩺 Stability & Availability | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -eu

rg -n -C 8 \
  '(node-version|npm (ci|install|run)|cross-env|engine-strict)' \
  .github/workflows/release-manual-docs.yml package.json .npmrc 2>/dev/null || true

Repository: parse-community/parse-server

Length of output: 6312


🏁 Script executed:

#!/bin/bash
set -eu

echo "== release-manual-docs workflow =="
cat -n .github/workflows/release-manual-docs.yml

echo
echo "== release_docs.sh =="
if [ -f release_docs.sh ]; then
  cat -n release_docs.sh
fi

echo
echo "== package.json engines/scripts around docs =="
cat -n package.json | sed -n '110,150p'

Repository: parse-community/parse-server

Length of output: 6436


Update the manual docs workflow to Node 20+. .github/workflows/release-manual-docs.yml still pins node-version: 18.20.4, but that job runs npm ci and ./release_docs.sh, so it will hit the repo’s Node 20+ toolchain requirements and can break docs releases.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@package.json` at line 85, Update the node-version setting in the manual docs
workflow to Node 20 or newer, ensuring the job running npm ci and
release_docs.sh uses the repository’s supported toolchain. Keep the existing
workflow behavior unchanged.

@codecov

codecov Bot commented Jul 14, 2026

Copy link
Copy Markdown

Codecov Report

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

Additional details and impacted files
@@            Coverage Diff             @@
##            alpha   #10579      +/-   ##
==========================================
- Coverage   92.68%   92.28%   -0.40%     
==========================================
  Files         193      193              
  Lines       17025    17025              
  Branches      248      248              
==========================================
- Hits        15779    15712      -67     
- Misses       1225     1288      +63     
- Partials       21       25       +4     

☔ View full report in Codecov by Harness.
📢 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.

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