refactor: Bump @babel/preset-env from 7.29.2 to 7.29.7

[mtrezza]

Closes #10589

Changes

Bumps the direct devDependency @babel/preset-env from 7.29.2 to 7.29.7 (patch-level release). Replaces the Dependabot PR #10589.

Breaking

None. Patch-level bump of a build-time-only devDependency (the Babel preset used for transpilation); no runtime or public API impact.

Code Changes

• package.json: @babel/preset-env 7.29.2 -> 7.29.7.
• package-lock.json: updated to match, scoped to the @babel/preset-env subtree.

Summary by CodeRabbit

• Chores
  • Updated the Babel development tooling to version 7.29.7.
  • Refreshed the project’s dependency lockfile to reflect the updated tooling packages.

[parse-github-assistant]

🚀 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]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 647ce8a5-cd25-41ed-bce9-a7791ce03dd8

📥 Commits

Reviewing files that changed from the base of the PR and between b45f7ea and f72ff5c.

📒 Files selected for processing (2)

• package-lock.json
• package.json

---

📝 Walkthrough

Walkthrough

Updates @babel/preset-env from 7.29.2 to 7.29.7 and synchronizes related Babel packages, resolved URLs, integrity hashes, and dependency requirements in the lockfile.

Changes

Babel dependency update

Layer / File(s)	Summary
Babel version alignment package.json, package-lock.json	Updates @babel/preset-env to 7.29.7 and refreshes its locked Babel helpers, plugins, metadata, integrity values, and transitive requirements.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

• parse-community/parse-server#10588: Updates overlapping Babel packages in package-lock.json, including @babel/core and related dependencies.

Suggested reviewers: semantic-release-bot

🚥 Pre-merge checks | ✅ 7

✅ Passed checks (7 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title matches the dependency bump and uses the required refactor: prefix.
Description check	✅ Passed	The description covers the issue, approach, impact, and code changes, though it omits the task checklist from the template.
Linked Issues check	✅ Passed	The changes update @babel/preset-env from 7.29.2 to 7.29.7 as requested in #10589.
Out of Scope Changes check	✅ Passed	The lockfile dependency churn is tied to the Babel bump and no unrelated changes are present.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Security Check	✅ Passed	PASS: The bump only updates @babel/preset-env and its Babel subtree to 7.29.7 from registry.npmjs.org; no suspicious sources/scripts, and it stays above the fixed GHSA range.
Engage In Review Feedback	✅ Passed	PASS: The PR shows “No reviews” and only bot comments, so there was no review feedback to ignore or resolve.

✨ 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.3.8)

package.json

Traceback (most recent call last):
File "/usr/local/bin/checkov", line 2, in
from checkov.main import Checkov
ModuleNotFoundError: No module named 'checkov'

package-lock.json

Traceback (most recent call last):
File "/usr/local/bin/checkov", line 2, in
from checkov.main import Checkov
ModuleNotFoundError: No module named 'checkov'

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.69%. Comparing base (b45f7ea) to head (f72ff5c).

Additional details and impacted files

@@           Coverage Diff           @@
##            alpha   #10592   +/-   ##
=======================================
  Coverage   92.69%   92.69%           
=======================================
  Files         193      193           
  Lines       17027    17027           
  Branches      248      248           
=======================================
  Hits        15784    15784           
  Misses       1222     1222           
  Partials       21       21           

☔ 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.