chore: 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

• Dockerfile (dockerfile)
• .github/workflows/ci.yml (github-actions)
• .github/workflows/container.yaml (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
• Provide a link to octochangelog's improved breakdown for Renovate's changelogs

---

What to Expect

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

chore(deps): update dependency concurrently to v9.2.4

• Schedule: ["at any time"]
• Branch name: renovate/concurrently-9.x-lockfile
• Merge into: main
• Upgrade concurrently to 9.2.4

chore(deps): update dependency tar to v7.5.20

• Schedule: ["at any time"]
• Branch name: renovate/tar-7.x-lockfile
• Merge into: main
• Upgrade tar to 7.5.20

chore(deps): update dependency vitest to v3.2.7

• Schedule: ["at any time"]
• Branch name: renovate/vitest-monorepo
• Merge into: main
• Upgrade vitest to 3.2.7

chore(deps): update eslint monorepo to v9.39.5

• Schedule: ["at any time"]
• Branch name: renovate/eslint-monorepo
• Merge into: main
• Upgrade @eslint/js to 9.39.5
• Upgrade eslint to 9.39.5

chore(deps): update commitlint monorepo to v21.2.1

• Schedule: ["at any time"]
• Branch name: renovate/commitlint-monorepo
• Merge into: main
• Upgrade @commitlint/cli to 21.2.1
• Upgrade @commitlint/config-conventional to 21.2.0

chore(deps): update dependency @​fastify/cors to v11.3.0

• Schedule: ["at any time"]
• Branch name: renovate/fastify-cors-11.x-lockfile
• Merge into: main
• Upgrade @fastify/cors to 11.3.0

chore(deps): update dependency @​fastify/swagger to v9.8.1

• Schedule: ["at any time"]
• Branch name: renovate/fastify-swagger-9.x-lockfile
• Merge into: main
• Upgrade @fastify/swagger to 9.8.1

chore(deps): update dependency @​fastify/swagger-ui to v6.1.0

• Schedule: ["at any time"]
• Branch name: renovate/fastify-swagger-ui-6.x-lockfile
• Merge into: main
• Upgrade @fastify/swagger-ui to 6.1.0

chore(deps): update dependency @​patternfly/react-core to v6.6.0

• Schedule: ["at any time"]
• Branch name: renovate/patternfly-react-core-6.x-lockfile
• Merge into: main
• Upgrade @patternfly/react-core to 6.6.0

chore(deps): update dependency @​patternfly/react-icons to v6.6.0

• Schedule: ["at any time"]
• Branch name: renovate/patternfly-react-icons-6.x-lockfile
• Merge into: main
• Upgrade @patternfly/react-icons to 6.6.0

chore(deps): update dependency @​patternfly/react-table to v6.6.0

• Schedule: ["at any time"]
• Branch name: renovate/patternfly-react-table-6.x-lockfile
• Merge into: main
• Upgrade @patternfly/react-table to 6.6.0

chore(deps): update dependency @​types/node to v22.20.1

• Schedule: ["at any time"]
• Branch name: renovate/node-22.x-lockfile
• Merge into: main
• Upgrade @types/node to 22.20.1

chore(deps): update dependency fastify to v5.10.0

• Schedule: ["at any time"]
• Branch name: renovate/fastify-5.x-lockfile
• Merge into: main
• Upgrade fastify to 5.10.0

chore(deps): update dependency fuse.js to v7.5.0

• Schedule: ["at any time"]
• Branch name: renovate/fuse.js-7.x-lockfile
• Merge into: main
• Upgrade fuse.js to 7.5.0

chore(deps): update dependency js-yaml to v4.3.0

• Schedule: ["at any time"]
• Branch name: renovate/js-yaml-4.x-lockfile
• Merge into: main
• Upgrade js-yaml to 4.3.0

chore(deps): update dependency tsx to v4.23.1

• Schedule: ["at any time"]
• Branch name: renovate/tsx-4.x-lockfile
• Merge into: main
• Upgrade tsx to 4.23.1

chore(deps): update dependency typescript-eslint to v8.64.0

• Schedule: ["at any time"]
• Branch name: renovate/typescript-eslint-monorepo
• Merge into: main
• Upgrade typescript-eslint to 8.64.0

chore(deps): update actions/checkout action to v7

• Schedule: ["at any time"]
• Branch name: renovate/actions-checkout-7.x
• Merge into: main
• Upgrade actions/checkout to 9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0

chore(deps): update actions/setup-node action to v7

• Schedule: ["at any time"]
• Branch name: renovate/actions-setup-node-7.x
• Merge into: main
• Upgrade actions/setup-node to 820762786026740c76f36085b0efc47a31fe5020

chore(deps): update dependency @​vitejs/plugin-react to v6

• Schedule: ["at any time"]
• Branch name: renovate/vitejs-plugin-react-6.x
• Merge into: main
• Upgrade @vitejs/plugin-react to ^6.0.0

chore(deps): update dependency concurrently to v10

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

chore(deps): update dependency node to v24

• Schedule: ["at any time"]
• Branch name: renovate/node-24.x
• Merge into: main
• Upgrade node to 24
• Upgrade @types/node to ^24.0.0

chore(deps): update dependency typescript to v7

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

chore(deps): update dependency vite to v8

• Schedule: ["at any time"]
• Branch name: renovate/vite-8.x
• Merge into: main
• Upgrade vite to ^8.0.0

chore(deps): update dependency vitest to v4

• Schedule: ["at any time"]
• Branch name: renovate/major-vitest-monorepo
• Merge into: main
• Upgrade vitest to ^4.0.0

chore(deps): update docker/build-push-action action to v7

• Schedule: ["at any time"]
• Branch name: renovate/docker-build-push-action-7.x
• Merge into: main
• Upgrade docker/build-push-action to v7

chore(deps): update docker/login-action action to v4

• Schedule: ["at any time"]
• Branch name: renovate/docker-login-action-4.x
• Merge into: main
• Upgrade docker/login-action to v4

chore(deps): update docker/metadata-action action to v6

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

chore(deps): update docker/setup-buildx-action action to v4

• Schedule: ["at any time"]
• Branch name: renovate/docker-setup-buildx-action-4.x
• Merge into: main
• Upgrade docker/setup-buildx-action to v4

chore(deps): update eslint monorepo to v10

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

fix(deps): update dependency @​fastify/static to v10

• Schedule: ["at any time"]
• Branch name: renovate/fastify-static-10.x
• Merge into: main
• Upgrade @fastify/static to ^10.0.0

fix(deps): update dependency better-sqlite3 to v12

• Schedule: ["at any time"]
• Branch name: renovate/better-sqlite3-12.x
• Merge into: main
• Upgrade better-sqlite3 to ^12.0.0

fix(deps): update dependency js-yaml to v5

• Schedule: ["at any time"]
• Branch name: renovate/js-yaml-5.x
• Merge into: main
• Upgrade js-yaml to ^5.0.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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: renovate[bot]

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[openshift-ci]

Hi @renovate[bot]. Thanks for your PR.

I'm waiting for a redhat-ai-dev member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.