Skip to content

Conversation

@red-hat-konflux
Copy link
Contributor

This PR contains the following updates:

Package Change Age Confidence
stylelint-config-standard ^39.0.1 -> ^40.0.0 age confidence

Release Notes

stylelint/stylelint-config-standard (stylelint-config-standard)

v40.0.0

Compare Source

  • Removed: stylelint less than 17.0.0 from peer dependencies.
  • Removed: support for Node.js less than 20.19.0.
  • Changed: updated to stylelint-config-recommended@18.0.0.
  • Changed: module type to ESM.

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 error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: lightspeed-console-plugin@1.0.9
npm error Found: stylelint@16.26.1
npm error node_modules/stylelint
npm error   dev stylelint@"^16.26.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peer stylelint@"^17.0.0" from stylelint-config-standard@40.0.0
npm error node_modules/stylelint-config-standard
npm error   dev stylelint-config-standard@"^40.0.0" 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_48_574Z-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_48_574Z-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 xrajesh 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 6e294ec link true /test fips-image-scan-service
ci/prow/images 6e294ec link true /test images
ci/prow/i18n 6e294ec link true /test i18n
ci/prow/lint 6e294ec 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