Skip to content

refactor: Bump browserslist from 4.16.6 to 4.29.4 - #228

Merged
mtrezza merged 1 commit into
parse-community:masterfrom
mtrezza:refactor/browserslist-4.29.4
Oct 24, 2026
Merged

mtrezza merged 1 commit into
parse-community:masterfrom
mtrezza:refactor/browserslist-4.29.4

Conversation

@mtrezza

@mtrezza mtrezza commented Oct 24, 2026 •

Copy link
Copy Markdown
Member

Closes #221

Bot PR #221 targeted browserslist 4.28.8. browserslist 4.28.9 and 4.29.0 to 4.29.4 were released after that PR was opened, and npm update browserslist now resolves to 4.29.4, so this PR upgrades to 4.29.4. This stays within browserslist major version 4, and the parent's ^4.14.5 range allows it.

Security

browserslist is a transitive, development-only dependency (nyc → istanbul-lib-instrument → @babel/core → @babel/helper-compilation-targets → browserslist).

Lock File Changes

Only package-lock.json changes, limited to browserslist and its own dependencies:

  • browserslist 4.16.6 → 4.29.4
  • caniuse-lite 1.0.30001230 → 1.0.30001819 (browser support data; previously nested under browserslist, now hoisted)
  • electron-to-chromium 1.3.739 → 1.5.464 (Electron to Chromium version data; previously nested under browserslist, now hoisted)
  • node-releases 1.1.71 → 2.0.60 (Node.js release data; browserslist 4.29.4 requires ^2.0.59; declares engines >=18, compatible with this repository's Node 20, 22 and 24)
  • escalade 3.1.1 → 3.2.0. This is a shared, hoisted entry:
    • browserslist 4.16.6 depended on it directly (^3.1.1). In 4.29.4 it comes in through update-browserslist-db, which requires ^3.2.0.
    • It is also used by the yargs copies under mocha (yargs 16.2.0), semantic-release (yargs 18.0.0) and cli-highlight (yargs 16.2.0). Their ^3.1.1 ranges still accept 3.2.0.
    • 3.1.2 added TypeScript nodenext resolution support, and 3.2.0 ships separate ESM and CommonJS TypeScript definitions. Neither release changes runtime behavior.
  • update-browserslist-db 1.3.4 (added; the caniuse-lite update CLI that browserslist 4.21.0 split out of browserslist --update-db; not run by this repository)
  • baseline-browser-mapping 2.11.32 (added; data for the Baseline queries added in browserslist 4.26.0; declares engines >=6.0.0; not affected by GHSA-w5vr-8v7q-w6rv, which is fixed in 2.11.0)
  • colorette 1.2.2 (removed; only browserslist 4.16.6 used it)

Changes

browserslist 4.16.6 → 4.29.4

The query result changes in this range (IE 11 moved to dead in 4.21.0, Baidu moved to dead in 4.20.3, and the Firefox ESR data updates) do not affect this repository. The only consumer is @babel/helper-compilation-targets 7.13.8, which Babel calls during nyc coverage instrumentation. It calls browserslist.loadConfig({ config, path, env }) and then browserslist(queries, { mobileToDesktop: true }). istanbul-lib-instrument 4.0.3 runs Babel with configFile: false and babelrc: false and sets no targets, and this repository has no browserslist config. So loadConfig returns undefined, and Babel resolves an empty query list with no browser targets. Both APIs keep their signatures from 4.16.6 to 4.29.4. With caniuse-lite 1.0.30001819, the "Browserslist: caniuse-lite is outdated" warning that npm run coverage printed with the 2021 data goes away.

Breaking Changes

None

Code Changes Required

None — the upgrade is a drop-in replacement.

@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 Oct 24, 2026

Copy link
Copy Markdown

Warning

Review limit reached

The included review limit has been reached and this organization has disabled usage-based review continuation. Wait for reviews to reset or ask a billing admin to change After included review limits.

  • Ask an admin to enable usage-based reviews

Open in CodeRabbit

Reviews can continue after your included limit without a manual trigger. An admin must approve usage-based billing.

Next included review available in 1 minute.

Check out review usage here.

View limit details

Limit details: You’ve used all 2 included reviews currently available. Your 54 included PR review attempts over the past 7 days set your current allowance at 2 reviews per hour.

Learn how review limits work.

Review configuration:

Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Essentials
  • Run ID: 9f3b828e-559a-4b54-acb1-6f82bb180278
Commits

Reviewing files that changed from the base of the PR and between fbdc137 and eecc07c.

Files selected for processing: 1
  • package-lock.json
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

@codecov

codecov Bot commented Oct 24, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.87%. Comparing base (fbdc137) to head (eecc07c).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #228   +/-   ##
=======================================
  Coverage   95.87%   95.87%           
=======================================
  Files          23       23           
  Lines         849      849           
=======================================
  Hits          814      814           
  Misses         35       35           

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

@mtrezza
mtrezza merged commit 7a4c21d into parse-community:master Oct 24, 2026
8 checks passed
@mtrezza
mtrezza deleted the refactor/browserslist-4.29.4 branch October 24, 2026 19:44
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