Skip to content

chore: Update lint related libraries#26051

Merged
Gudahtt merged 1 commit intomainfrom
update-lint-libraries
Feb 13, 2026
Merged

chore: Update lint related libraries#26051
Gudahtt merged 1 commit intomainfrom
update-lint-libraries

Conversation

@Gudahtt
Copy link
Copy Markdown
Member

@Gudahtt Gudahtt commented Feb 12, 2026 •
edited by cursor bot
Loading

Description

Update lint related libraries to help prepare for the update to ESLint v9.

Changelog

CHANGELOG entry: null

Related issues

N/A

Manual testing steps

N/A

Screenshots/Recordings

N/A

Pre-merge author checklist

Pre-merge reviewer checklist

  • I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
  • I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

Note

Low Risk
Lockfile-only updates to dev-time lint tooling; main risk is CI/editor lint behavior changes or new lint failures, not runtime impact.

Overview
Updates the yarn.lock to pull newer lint/tooling dependencies, primarily upgrading eslint-plugin-import (2.27.5 → 2.32.0), eslint-plugin-react (7.35.0 → 7.37.5), and eslint-plugin-react-native (4.0.0 → 4.1.0).

These upgrades cascade into refreshed resolver/utility packages (e.g., eslint-import-resolver-node, eslint-module-utils, tsconfig-paths) and a broad set of transitive dependency bumps (notably es-abstract and related polyfill helpers) to align with upcoming ESLint v9 compatibility.

Written by Cursor Bugbot for commit 75732ae. This will update automatically on new commits. Configure here.

@metamaskbot metamaskbot added the team-core-platform Core Platform team label Feb 12, 2026
@socket-security
Copy link
Copy Markdown

socket-security bot commented Feb 12, 2026 •
edited
Loading

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security		 Vulnerability Quality Maintenance License
Updatednpm/​eslint-plugin-react-native@​4.0.0 ⏵ 4.1.0100 +110010080100
Updatednpm/​eslint-plugin-import@​2.27.5 ⏵ 2.32.098 +110010084100

View full report

@socket-security
Copy link
Copy Markdown

socket-security bot commented Feb 12, 2026 •
edited
Loading

Warning

MetaMask internal reviewing guidelines:

  • Do not ignore-all
  • Each alert has instructions on how to review if you don't know what it means. If lost, ask your Security Liaison or the supply-chain group
  • Copy-paste ignore lines for specific packages or a group of one kind with a note on what research you did to deem it safe.
    @SocketSecurity ignore npm/PACKAGE@VERSION
Action Severity Alert  (click "▶" to expand/collapse)
Warn Low
Potential code anomaly (AI signal): npm es-abstract is 100.0% likely to have a medium risk anomaly

Notes: The analyzed code is a faithful, standard implementation of ECMAScript FlattenIntoArray with optional mapper support and depth control. No malicious activity detected within this fragment. The main risk vector is user-provided mapperFunction execution, which is a normal pattern for functional transforms and should be reviewed in the hosting environment for trust and sandboxing. Overall security posture in isolation is low to moderate, contingent on mapperFunction usage.

Confidence: 1.00

Severity: 0.60

From: ? → npm/@storybook/react-native@6.5.6 → npm/eslint-plugin-react@7.34.1 → npm/@react-native/eslint-config@0.76.9 → npm/enzyme@3.9.0 → npm/enzyme-adapter-react-16@1.10.0 → npm/eslint-plugin-import@2.32.0 → npm/es-abstract@1.24.1

ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/es-abstract@1.24.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@Gudahtt
chore: Update lint related libraries
75732ae 
Update lint related libraries to help prepare for the update to ESLint
v9.
@Gudahtt Gudahtt marked this pull request as ready for review February 12, 2026 23:29
@Gudahtt Gudahtt force-pushed the update-lint-libraries branch from bab11a1 to 75732ae Compare February 12, 2026 23:29
@Gudahtt
Copy link
Copy Markdown
Member Author

Gudahtt commented Feb 12, 2026

These updates were generated by running:

yarn up -R @typescript-eslint/eslint-plugin \
@typescript-eslint/parser \
@typescript-eslint/type-utils \
@typescript-eslint/utils \
eslint-plugin-import \
eslint-plugin-jsdoc \
eslint-plugin-react-hooks \
eslint-plugin-react-native \
eslint-plugin-react

Those are all of the dependencies (excluding our shared ESLint config) that depend upon ESLint v8.

@Gudahtt Gudahtt enabled auto-merge February 12, 2026 23:31
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Feb 12, 2026

🔍 Smart E2E Test Selection

  • Selected E2E tags: None (no tests recommended)
  • Selected Performance tags: None (no tests recommended)
  • Risk Level: low
  • AI Confidence: 95%
click to see 🤖 AI reasoning details

E2E Test Selection:
This PR only modifies yarn.lock with updates to development dependencies - specifically ESLint plugins (eslint-plugin-import 2.27.5→2.32.0, eslint-plugin-react 7.35.0→7.37.5, eslint-plugin-react-native 4.0.0→4.1.0) and their transitive dependencies (es-abstract, es-iterator-helpers, various is-* and array-* utility packages). These are all development-time linting tools that have zero impact on the application's runtime behavior. No application source code, test infrastructure, or configuration files were changed. The lockfile updates will be validated by the CI linting step itself. No E2E tests are required for this change.

Performance Test Selection:
This PR only updates development dependencies (ESLint plugins and their transitive dependencies) in yarn.lock. These are linting tools used during development and CI, not runtime dependencies. They have no impact on app performance, UI rendering, data loading, or any user-facing functionality. No performance tests are needed.

View GitHub Actions results

Cal-L
Cal-L approved these changes Feb 12, 2026
View reviewed changes
Copy link
Copy Markdown
Contributor

@Cal-L Cal-L left a comment

Choose a reason for hiding this comment

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

LGTM

@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud bot commented Feb 12, 2026

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

@Gudahtt Gudahtt added this pull request to the merge queue Feb 12, 2026
Merged via the queue into main with commit 1082278 Feb 13, 2026
62 of 63 checks passed
@Gudahtt Gudahtt deleted the update-lint-libraries branch February 13, 2026 00:12
@github-actions github-actions bot locked and limited conversation to collaborators Feb 13, 2026
@metamaskbot metamaskbot added the release-7.67.0 Issue or pull request that will be included in release 7.67.0 label Feb 13, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

@Cal-L Cal-L Cal-L approved these changes

@sleepytanya sleepytanya sleepytanya approved these changes

Assignees

No one assigned

Labels

release-7.67.0 Issue or pull request that will be included in release 7.67.0 team-core-platform Core Platform team

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@Gudahtt @Cal-L @sleepytanya @metamaskbot