Configure Renovate

[renovate]

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

📚 See our Reading List for relevant documentation you may be interested in reading.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.

---

Detected Package Files

• composer.json (composer)
• .github/workflows/codecov.yml (github-actions)
• .github/workflows/continuous-integration.yml (github-actions)
• .github/workflows/qodana_code_quality.yml (github-actions)
• .github/workflows/static-analysis.yml (github-actions)
• package.json (npm)

Configuration Summary

Based on the default config's presets, Renovate will:

• Start dependency updates only once this onboarding PR is merged
• Hopefully safe environment variables to allow users to configure.
• Show all Merge Confidence badges for pull requests.
• Enable Renovate Dependency Dashboard creation.
• Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
• Ignore node_modules, bower_components, vendor and various test/tests (except for nuget) directories.
• Group known monorepo packages together.
• Use curated list of recommended non-monorepo package groupings.
• Show only the Age and Confidence Merge Confidence badges for pull requests.
• Apply crowd-sourced package replacement rules.
• Apply crowd-sourced workarounds for known problems with packages.
• Ensure that every dependency pinned by digest and sourced from Forgejo contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from GitLab.com contains a link to the commit-to-commit diff
• Correctly link to the source code for golang.org/x packages
• Link to pkg.go.dev/... for golang.org/x packages' title

---

What to Expect

With your current configuration, Renovate will create 19 Pull Requests:

Update dependency shx to ^0.4.0

• Schedule: ["at any time"]
• Branch name: renovate/shx-0.x
• Merge into: 7.0
• Upgrade shx to ^0.4.0

Update codecov/codecov-action action to v6

• Schedule: ["at any time"]
• Branch name: renovate/codecov-codecov-action-6.x
• Merge into: 7.0
• Upgrade codecov/codecov-action to v6

Update dependency babel-loader to v10

• Schedule: ["at any time"]
• Branch name: renovate/babel-loader-10.x
• Merge into: 7.0
• Upgrade babel-loader to ^10.0.0

Update dependency copy-webpack-plugin to v14

• Schedule: ["at any time"]
• Branch name: renovate/copy-webpack-plugin-14.x
• Merge into: 7.0
• Upgrade copy-webpack-plugin to ^14.0.0

Update dependency cross-env to v10

• Schedule: ["at any time"]
• Branch name: renovate/cross-env-10.x
• Merge into: 7.0
• Upgrade cross-env to ^10.0.0

Update dependency css-loader to v7

• Schedule: ["at any time"]
• Branch name: renovate/css-loader-7.x
• Merge into: 7.0
• Upgrade css-loader to 7.1.4

Update dependency css-minimizer-webpack-plugin to v8

• Schedule: ["at any time"]
• Branch name: renovate/css-minimizer-webpack-plugin-8.x
• Merge into: 7.0
• Upgrade css-minimizer-webpack-plugin to ^8.0.0

Update dependency dotkernel/dot-navigation to v4

• Schedule: ["at any time"]
• Branch name: renovate/dotkernel-dot-navigation-4.x
• Merge into: 7.0
• Upgrade dotkernel/dot-navigation to ^4.0.0

Update dependency dotkernel/dot-rbac-guard to v4

• Schedule: ["at any time"]
• Branch name: renovate/dotkernel-dot-rbac-guard-4.x
• Merge into: 7.0
• Upgrade dotkernel/dot-rbac-guard to ^4.0.0

Update dependency eslint to v10

• Schedule: ["at any time"]
• Branch name: renovate/major-eslint-monorepo
• Merge into: 7.0
• Upgrade eslint to ^10.0.0

Update dependency jquery to v4

• Schedule: ["at any time"]
• Branch name: renovate/jquery-4.x
• Merge into: 7.0
• Upgrade jquery to ^4.0.0

Update dependency phpunit/phpunit to v13

• Schedule: ["at any time"]
• Branch name: renovate/phpunit-phpunit-13.x
• Merge into: 7.0
• Upgrade phpunit/phpunit to ^13.0.0

Update dependency postcss-preset-env to v11

• Schedule: ["at any time"]
• Branch name: renovate/postcss-preset-env-11.x
• Merge into: 7.0
• Upgrade postcss-preset-env to ^11.0.0

Update dependency sass-loader to v17

• Schedule: ["at any time"]
• Branch name: renovate/sass-loader-17.x
• Merge into: 7.0
• Upgrade sass-loader to ^17.0.0

Update dependency stylelint to v17

• Schedule: ["at any time"]
• Branch name: renovate/stylelint-17.x
• Merge into: 7.0
• Upgrade stylelint to ^17.0.0

Update dependency stylelint-config-standard to v40

• Schedule: ["at any time"]
• Branch name: renovate/stylelint-config-standard-40.x
• Merge into: 7.0
• Upgrade stylelint-config-standard to ^40.0.0

Update dependency webpack-cli to v7

• Schedule: ["at any time"]
• Branch name: renovate/webpack-cli-7.x
• Merge into: 7.0
• Upgrade webpack-cli to ^7.0.0

Update JetBrains/qodana-action action to v2026

• Schedule: ["at any time"]
• Branch name: renovate/jetbrains-qodana-action-2026.x
• Merge into: 7.0
• Upgrade JetBrains/qodana-action to v2026.1.0

Update symfony packages to v8

• Schedule: ["at any time"]
• Branch name: renovate/major-symfony
• Merge into: 7.0
• Upgrade symfony/var-dumper to ^8.0.0
• Upgrade symfony/var-exporter to ^6.4 || ^7.4 || ^8.0

🚸 PR creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for prHourlyLimit for details.

---

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.

---

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

[github-actions]

Qodana for JS

It seems all right 👌

No new problems were found according to the checks applied

💡 Qodana analysis was run in the pull request mode: only the changed files were checked
☁️ View the detailed Qodana report

Contact Qodana team

Contact us at qodana-support@jetbrains.com

• Or via our issue tracker: https://jb.gg/qodana-issue
• Or share your feedback: https://jb.gg/qodana-discussions