Skip to content

style(deps): update dependency stylelint to v17#1006

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/major-17-style-tools
Open

style(deps): update dependency stylelint to v17#1006
renovate[bot] wants to merge 1 commit intomainfrom
renovate/major-17-style-tools

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 14, 2026

This PR contains the following updates:

Package Change Age Confidence
stylelint (source) ^15.11.0 || 16.x^15.11.0 || 16.x || 17.x age confidence

Release Notes

stylelint/stylelint (stylelint)

v17.4.0

Compare Source

It adds 2 options to the rules and fixes 7 bugs.

v17.3.0

Compare Source

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.

v17.2.0

Compare Source

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.

v17.1.1

Compare Source

It fixes 2 bugs.

v17.1.0

Compare Source

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.

v17.0.0

Compare Source

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.

  • Removed: CommonJS Node.js API (#​8859) (@​jeddy3).
  • Removed: output property in the Node.js API returned resolved object (#​8878) (@​jeddy3).
  • Removed: support for Node.js less than 20.19.0 (#​8867) (@​jeddy3).
  • Removed: GitHub formatter (#​8888) (@​jeddy3).
  • Removed: resolveNestedSelectors option from selector-class-pattern (#​8931) (@​jeddy3).
  • Removed: checkContextFunctionalPseudoClasses option from selector-max-id (#​8913) (@​jeddy3).
  • Changed: default fix mode to strict (#​8889) (@​jeddy3).
  • Changed: report to be consistent and predictable in how it handles the provided position arguments (#​8217) (@​romainmenke).
  • Changed: selector-max-* syntax rules for standard CSS nesting and modern functional pseudo-classes (#​8913) (@​jeddy3).
  • Changed: *-specificity semantic rules for standard CSS nesting (#​8913) (@​jeddy3).
  • Changed: no-duplicate-selectors and selector-no-qualifying-type for standard CSS nesting (#​8913) (@​jeddy3).
  • Changed: *-list rules to have consistent behaviour for vendor prefixes and case (#​8912) (@​jeddy3).
  • Changed: *-no-vendor-prefix rules to have consistent behaviour for their ignore*: [] secondary options (#​8924) (@​jeddy3).
  • Changed: declaration-property-max-values rule to have consistent behaviour for vendor prefixes (#​8926) (@​jeddy3).
  • Added: except: ["after-block"] to custom-property-empty-line-before (#​8921) (@​kovsu).
  • Added: except: ["after-block"] to declaration-empty-line-before (#​8910) (@​kovsu).
  • Added: ignoreSelectors: [] to no-duplicate-selectors (#​8883) (@​kovsu).
  • Fixed: Windows drive letter casing inconsistencies when matching patterns against file paths (#​8941) (@​adalinesimonian).
  • Fixed: CLI help to include TypeScript config files (#​8908) (@​kovsu).
  • Fixed: at-rule-descriptor-no-unknown false positives for declarations within feature-value-blocks (#​8868) (@​kovsu).
  • Fixed: declaration-block-no-redundant-longhand-properties false negatives for short and long combinations (#​8892) (@​nathannewyen).
  • Fixed: media-feature-name-no-unknown false positives for namespaced dollar variables and range context queries (#​8890) (@​kovsu).
  • Fixed: nesting-selector-no-missing-scoping-root false positives for CSS-in-JS (#​8905) (@​kovsu).
  • Fixed: no-invalid-position-declaration false negatives for embedded blocks (#​8907) (@​kovsu).
  • Fixed: selector-no-qualifying-type false negatives for :is/where() (#​8940) (@​romainmenke).
  • Fixed: selector-type-no-unknown false positives for MathML 4 tags (#​8874) (@​jeddy3).

Configuration

📅 Schedule: Branch creation - "after 1am and before 5am every weekend" in timezone Europe/Berlin, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

BREAKING CHANGE: updated dependencies to major versions
@renovate renovate bot added the style label Mar 14, 2026
@renovate renovate bot requested a review from prisis as a code owner March 14, 2026 01:08
@renovate renovate bot added the style label Mar 14, 2026
@renovate
Copy link
Contributor Author

renovate bot commented Mar 14, 2026

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml
Scope: all 8 workspace projects
 ERR_PNPM_CATALOG_ENTRY_NOT_FOUND_FOR_SPEC  No catalog entry '@tsconfig/node16' was found for catalog 'tsc'.

@github-actions
Copy link
Contributor

Hey there and thank you for opening this pull request! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.

Details:

Unknown release type "style" found in pull request title "style(deps): update dependency stylelint to v17".

Available types:
 - build
 - chore
 - ci
 - docs
 - feat
 - fix
 - perf
 - infra
 - refactor
 - revert
 - test

@socket-security
Copy link

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Obfuscated code: npm entities is 91.0% likely obfuscated

Confidence: 0.91

Location: Package overview

From: pnpm-lock.yamlnpm/entities@4.5.0

ℹ Read more on: This package | This alert | What is obfuscated code?

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 not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/entities@4.5.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 High
Obfuscated code: npm entities is 91.0% likely obfuscated

Confidence: 0.91

Location: Package overview

From: pnpm-lock.yamlnpm/astro-eslint-parser@1.3.0npm/entities@6.0.0

ℹ Read more on: This package | This alert | What is obfuscated code?

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 not obfuscate their code. Consider not using packages with obfuscated code.

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

View full report

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants