Skip to content

Conversation

@red-hat-konflux
Copy link
Contributor

This PR contains the following updates:

Package Change Age Confidence
stylelint (source) ^16.26.1 -> ^17.0.0 age confidence

Release Notes

stylelint/stylelint (stylelint)

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 - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, 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

To execute skipped test pipelines write comment /ok-to-test.


Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
@red-hat-konflux
Copy link
Contributor Author

⚠️ 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: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: stylelint-config-recommended@17.0.0
npm warn Found: stylelint@17.0.0
npm warn node_modules/stylelint
npm warn   dev stylelint@"^17.0.0" from the root project
npm warn
npm warn Could not resolve dependency:
npm warn peer stylelint@"^16.23.0" from stylelint-config-recommended@17.0.0
npm warn node_modules/stylelint-config-recommended
npm warn   stylelint-config-recommended@"^17.0.0" from stylelint-config-standard@39.0.1
npm warn   node_modules/stylelint-config-standard
npm warn
npm warn Conflicting peer dependency: stylelint@16.26.1
npm warn node_modules/stylelint
npm warn   peer stylelint@"^16.23.0" from stylelint-config-recommended@17.0.0
npm warn   node_modules/stylelint-config-recommended
npm warn     stylelint-config-recommended@"^17.0.0" from stylelint-config-standard@39.0.1
npm warn     node_modules/stylelint-config-standard
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: stylelint-config-standard@39.0.1
npm error Found: stylelint@17.0.0
npm error node_modules/stylelint
npm error   dev stylelint@"^17.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer stylelint@"^16.23.0" from stylelint-config-standard@39.0.1
npm error node_modules/stylelint-config-standard
npm error   dev stylelint-config-standard@"^39.0.1" from the root project
npm error
npm error Conflicting peer dependency: stylelint@16.26.1
npm error node_modules/stylelint
npm error   peer stylelint@"^16.23.0" from stylelint-config-standard@39.0.1
npm error   node_modules/stylelint-config-standard
npm error     dev stylelint-config-standard@"^39.0.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2026-01-22T08_10_42_695Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2026-01-22T08_10_42_695Z-debug-0.log

@openshift-ci openshift-ci bot requested review from syedriko and xrajesh January 22, 2026 08:14
@openshift-ci
Copy link

openshift-ci bot commented Jan 22, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign syedriko for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci
Copy link

openshift-ci bot commented Jan 22, 2026

@red-hat-konflux[bot]: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/fips-image-scan-service c2cb908 link true /test fips-image-scan-service
ci/prow/images c2cb908 link true /test images
ci/prow/lint c2cb908 link true /test lint

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

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.

0 participants