Skip to content

chore(deps-dev): bump stylelint from 15.11.0 to 17.3.0#2710

Open
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/stylelint-17.3.0
Open

chore(deps-dev): bump stylelint from 15.11.0 to 17.3.0#2710
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/stylelint-17.3.0

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 15, 2026 •
edited
Loading

Bumps stylelint from 15.11.0 to 17.3.0.

Release notes

Sourced from stylelint's releases.

17.3.0

It fixes 17 bugs. 3 related to supporting calc() in declaration-property-value-no-unknown, and 13 performance ones that make Stylelint a further 3x faster when using the rules in our standard config.

17.2.0

It fixes 7 bugs, including 5 performance ones that make Stylelint 7x faster and use 3x less memory on larger codebases such as design systems and monorepos. We also restructured our docs to create a contributor guide. If you'd like to help out and contribute to Stylelint, that's the place to start.

17.1.1

It fixes 2 bugs.

17.1.0

It fixes 5 bugs and adds the display-notation rule. Before we turn it on in our standard config, we'd like to hear the community's thoughts on which options to use.

17.0.0

It contains 14 breaking changes, which we've detailed in the migrating to 17.0.0 guide. Additionally, it adds 3 options to the rules and fixes 9 bugs. We've also released compatible versions of our shared config, Visual Studio Code extension, Node.js Rule Tester and Jest preset.

... (truncated)

Changelog

Sourced from stylelint's changelog.

17.3.0 - 2026-02-13

It fixes 17 bugs. 3 related to supporting calc() in declaration-property-value-no-unknown, and 13 performance ones that make Stylelint a further 3x faster when using the rules in our standard config.

17.2.0 - 2026-02-10

It fixes 7 bugs, including 5 performance ones that make Stylelint 7x faster and use 3x less memory on larger codebases such as design systems and monorepos. We also restructured our docs to create a contributor guide. If you'd like to help out and contribute to Stylelint, that's the place to start.

17.1.1 - 2026-02-03

It fixes 2 bugs.

17.1.0 - 2026-01-30

It fixes 5 bugs and adds the display-notation rule. Before we turn it on in our standard config, we'd like to hear the community's thoughts on which options to use.

... (truncated)

Commits
  • 6f1b667 Release 17.3.0 (#9078)
  • 10ea226 Refactor to consolidate walk* filter regexes (#9074)
  • a7b7cf9 Bump @csstools/css-calc (#9076)
  • a604c39 Document using languageOptions over secondary in `declaration-property-valu...
  • ff24683 Document extending syntax in applicable *-no-unknown rules (#9072)
  • 801f1f9 Document relationship between overlapping *-no-unknown rules (#9071)
  • bd952e7 Fix named-grid-areas-no-invalid false positives for mix of tabs and spaces ...
  • 239297d Fix declaration-property-value-no-unknown false negatives/positives for ma...
  • fcd18a5 Refactor CSSTree lexer creation (#9067)
  • e65319d Refactor typing via noUnusedLocals in tsconfig.json (#9069)
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for stylelint since your current version.

Install script changes

This version adds postprepare script and modifies prepare script that run during installation. Review the package contents before updating.


Dependabot compatibility score

You can trigger a rebase of this PR by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note

Medium Risk
Dev-tooling only, but this is a major stylelint upgrade with significant transitive dependency and Node engine requirement changes that could break CI or local linting.

Overview
Upgrades dev dependency stylelint from v15 to v17 (now ^17.4.0) and updates package-lock.json accordingly.

This pulls in a new set of stylelint transitive dependencies (notably newer postcss/cosmiconfig/globby stacks) and updates engine constraints for some of them (several now require newer Node versions), which may change lint behavior and compatibility.

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

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Feb 15, 2026

Assignees

The following users could not be added as assignees: protocol-galileo. Either the username does not exist or it does not have the correct permissions to be added as an assignee.

Please fix the above issues or remove invalid values from dependabot.yml.

@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Feb 15, 2026
@dependabot dependabot bot requested review from a team as code owners February 15, 2026 04:14
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Feb 15, 2026
@dependabot dependabot bot requested a review from a team as a code owner February 15, 2026 04:14
@dependabot dependabot bot added the javascript Pull requests that update javascript code label Feb 15, 2026
@vercel
Copy link

vercel bot commented Feb 15, 2026 •
edited
Loading

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
metamask-docs Error Error Mar 8, 2026 4:13am

Request Review

@dependabot dependabot bot mentioned this pull request Feb 15, 2026
Closed
@socket-security
Copy link

socket-security bot commented Feb 15, 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
Updatedstylelint@​15.11.0 ⏵ 17.4.098 +110010096100

View full report

@socket-security
Copy link

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

Caution

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)
Block Medium
Network access: npm cacheable in module globalThis["fetch"]

Module: globalThis["fetch"]

Location: Package overview

From: package-lock.json → npm/stylelint@17.4.0 → npm/cacheable@2.3.3

ℹ Read more on: This package | This alert | What is network access?

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: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/cacheable@2.3.3. 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.

Warn Low
Potential code anomaly (AI signal): npm ajv is 100.0% likely to have a medium risk anomaly

Notes: The code implements a standard AJV-like dynamic parser generator for JTD schemas. There are no explicit malware indicators in this fragment. The primary security concern is the dynamic code generation and execution from external schemas, which introduces a medium risk if schemas are untrusted. With trusted schemas and proper schema management, the risk is typically acceptable within this pattern.

Confidence: 1.00

Severity: 0.60

From: package-lock.json → npm/stylelint@17.4.0 → npm/ajv@8.18.0

ℹ 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/ajv@8.18.0. 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.

Warn Low
Potential code anomaly (AI signal): npm ajv is 100.0% likely to have a medium risk anomaly

Notes: The code implements standard timestamp validation with clear logic for normal and leap years and leap seconds. There is no network, file, or execution of external code within this isolated fragment. The only anomalous aspect is assigning a string to validTimestamp.code, which could enable external tooling to inject behavior in certain environments, but this does not constitute active malicious behavior in this isolated snippet. Overall, low to moderate security risk in typical usage; no malware detected within the shown code.

Confidence: 1.00

Severity: 0.60

From: package-lock.json → npm/stylelint@17.4.0 → npm/ajv@8.18.0

ℹ 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/ajv@8.18.0. 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.

Warn Low
Potential code anomaly (AI signal): npm ajv is 100.0% likely to have a medium risk anomaly

Notes: This module generates JavaScript code at runtime via standaloneCode(...) and then immediately executes it with require-from-string. Because the generated code can incorporate user-supplied schemas or custom keywords without sanitization or sandboxing, an attacker who controls those inputs could inject arbitrary code and achieve remote code execution in the Node process. Users should audit and lock down the standaloneCode output or replace dynamic evaluation with a safer, static bundling approach.

Confidence: 1.00

Severity: 0.60

From: package-lock.json → npm/stylelint@17.4.0 → npm/ajv@8.18.0

ℹ 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/ajv@8.18.0. 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.

Warn Low
Potential code anomaly (AI signal): npm css-tree is 100.0% likely to have a medium risk anomaly

Notes: The code is a standard, well-scoped parser fragment for a DSL-like FeatureFunction construct. It uses dynamic feature dispatch with proper balance checks and safe fallbacks, and emits a consistent AST node. No malicious behavior detected; the main risks relate to misconfiguration of the features map rather than code-level exploits.

Confidence: 1.00

Severity: 0.60

From: package-lock.json → npm/stylelint@17.4.0 → npm/css-tree@3.2.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/css-tree@3.2.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.

Warn Low
Potential code anomaly (AI signal): npm ignore is 100.0% likely to have a medium risk anomaly

Notes: The code fragment represents a conventional, well-structured path-ignore utility with caching and recursive parent-directory evaluation. Windows path normalization is present for compatibility but does not indicate malicious intent. No indicators of data leakage, external communication, or covert backdoors were found. Security impact primarily revolves around correct ignore semantics rather than intrinsic vulnerabilities. The component remains appropriate for use in a broader security-conscious pipeline if used with careful awareness of what is being ignored.

Confidence: 1.00

Severity: 0.60

From: package-lock.json → npm/stylelint@17.4.0 → npm/ignore@7.0.5

ℹ 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/ignore@7.0.5. 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

cursor[bot]
cursor bot reviewed Feb 15, 2026
View reviewed changes
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 2 potential issues.

package.json Outdated
"eslint": "^9.35.0",
"eslint-plugin-react": "^7.37.5",
"stylelint": "^15.0.0 ",
"stylelint": "^17.3.0",
Copy link

@cursor cursor bot Feb 15, 2026

Choose a reason for hiding this comment

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

Stylelint config peer version mismatch

Medium Severity

stylelint was upgraded to ^17.3.0, but stylelint-config-standard is still ^34.0.0, whose peer range in package-lock.json is stylelint: ^15.10.0. This creates an unsupported pairing that can break lint:style behavior or produce dependency resolution conflicts in installs.

Additional Locations (1)

Fix in Cursor Fix in Web

package-lock.json
},
"engines": {
"node": ">=20.19.0"
}
Copy link

@cursor cursor bot Feb 15, 2026

Choose a reason for hiding this comment

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

Node patch requirement now too strict

Medium Severity

The updated stylelint@17.3.0 now declares node >=20.19.0, while the project still advertises engines.node as 20.x. Environments on earlier Node 20 patch versions can now fail during install or when running lint:style.

Additional Locations (1)

Fix in Cursor Fix in Web

@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/stylelint-17.3.0 branch from f2ffe65 to 8cbea31 Compare February 22, 2026 04:12
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/stylelint-17.3.0 branch from 8cbea31 to 88e873a Compare March 1, 2026 04:12
@dependabot
chore(deps-dev): bump stylelint from 15.11.0 to 17.3.0
1cc7110 
Bumps [stylelint](https://github.com/stylelint/stylelint) from 15.11.0 to 17.3.0.
- [Release notes](https://github.com/stylelint/stylelint/releases)
- [Changelog](https://github.com/stylelint/stylelint/blob/main/CHANGELOG.md)
- [Commits](stylelint/stylelint@15.11.0...17.3.0)

---
updated-dependencies:
- dependency-name: stylelint
  dependency-version: 17.3.0
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/stylelint-17.3.0 branch from 88e873a to 1cc7110 Compare March 8, 2026 04:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@cursor cursor[bot] cursor[bot] left review comments

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants