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.

---

Detected Package Files

• .github/workflows/ci.yml (github-actions)
• .github/workflows/release.yml (github-actions)
• libs/base-reporter/package.json (npm)
• libs/jest-reporter/package.json (npm)
• libs/vitest-reporter/package.json (npm)
• package.json (npm)
• pnpm-workspace.yaml (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.

🔡 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.

---

What to Expect

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

Update dependency eslint to v8.57.1

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

Update dependency eslint-config-prettier to v9.1.2

• Schedule: ["at any time"]
• Branch name: renovate/eslint-config-prettier-9.x-lockfile
• Merge into: main
• Upgrade eslint-config-prettier to 9.1.2

Update dependency vitest to v1.6.1

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

Update actions/cache action to v4.2.4

• Schedule: ["at any time"]
• Branch name: renovate/actions-cache-4.x
• Merge into: main
• Upgrade actions/cache to v4.2.4

Update actions/checkout action to v4.3.0

• Schedule: ["at any time"]
• Branch name: renovate/actions-checkout-4.x
• Merge into: main
• Upgrade actions/checkout to v4.3.0

Update dependency @​types/node to v20.19.11

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

Update dependency envalid to v8.1.0

• Schedule: ["at any time"]
• Branch name: renovate/envalid-8.x-lockfile
• Merge into: main
• Upgrade envalid to 8.1.0

Update dependency eslint-import-resolver-typescript to v3.10.1

• Schedule: ["at any time"]
• Branch name: renovate/eslint-import-resolver-typescript-3.x-lockfile
• Merge into: main
• Upgrade eslint-import-resolver-typescript to 3.10.1

Update dependency eslint-plugin-import to v2.32.0

• Schedule: ["at any time"]
• Branch name: renovate/eslint-plugin-import-2.x-lockfile
• Merge into: main
• Upgrade eslint-plugin-import to 2.32.0

Update dependency eslint-plugin-jest-dom to v5.5.0

• Schedule: ["at any time"]
• Branch name: renovate/eslint-plugin-jest-dom-5.x-lockfile
• Merge into: main
• Upgrade eslint-plugin-jest-dom to 5.5.0

Update dependency husky to v9.1.7

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

Update dependency msw to v2.11.1

• Schedule: ["at any time"]
• Branch name: renovate/msw-2.x-lockfile
• Merge into: main
• Upgrade msw to 2.11.1

Update dependency prettier to v3.6.2

• Schedule: ["at any time"]
• Branch name: renovate/prettier-3.x-lockfile
• Merge into: main
• Upgrade prettier to 3.6.2

Update dependency tsx to v4.20.5

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

Update dependency typescript to ~5.9.0

• Schedule: ["at any time"]
• Branch name: renovate/typescript-5.x
• Merge into: main
• Upgrade typescript to ~5.9.0

Update nx monorepo to v19.8.14

• Schedule: ["at any time"]
• Branch name: renovate/nx-monorepo
• Merge into: main
• Upgrade @nx/eslint to 19.8.14
• Upgrade @nx/eslint-plugin to 19.8.14
• Upgrade @nx/workspace to 19.8.14
• Upgrade nx to 19.8.14

Update opentelemetry-js monorepo

• Schedule: ["at any time"]
• Branch name: renovate/opentelemetry-js-monorepo
• Merge into: main
• Upgrade @opentelemetry/core to 1.30.1
• Upgrade @opentelemetry/exporter-trace-otlp-http to ^0.203.0
• Upgrade @opentelemetry/exporter-trace-otlp-proto to ^0.203.0
• Upgrade @opentelemetry/otlp-exporter-base to ^0.203.0
• Upgrade @opentelemetry/resources to 1.30.1
• Upgrade @opentelemetry/sdk-trace-base to 1.30.1
• Upgrade @opentelemetry/semantic-conventions to 1.36.0

Update swc monorepo

• Schedule: ["at any time"]
• Branch name: renovate/swc-monorepo
• Merge into: main
• Upgrade @swc-node/register to ~1.11.0
• Upgrade @swc/cli to ^0.7.0
• Upgrade @swc/core to 1.13.5
• Upgrade @swc/helpers to 0.5.17

Update typescript-eslint monorepo to v7.18.0

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

Update actions/checkout action to v5

• Schedule: ["at any time"]
• Branch name: renovate/actions-checkout-5.x
• Merge into: main
• Upgrade actions/checkout to v5.0.0

Update dependency @faker-js/faker to v10

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

Update dependency @​types/node to v22

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

Update dependency chokidar to v4

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

Update dependency date-fns to v4

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

Update dependency eslint to v9

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

Update dependency eslint-config-prettier to v10

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

Update dependency eslint-import-resolver-typescript to v4

• Schedule: ["at any time"]
• Branch name: renovate/eslint-import-resolver-typescript-4.x
• Merge into: main
• Upgrade eslint-import-resolver-typescript to ^4.0.0

Update dependency vitest to v3

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

Update dependency yargs to v18

• Schedule: ["at any time"]
• Branch name: renovate/yargs-18.x
• Merge into: main
• Upgrade yargs to ^18.0.0

Update jest monorepo to v30 (major)

• Schedule: ["at any time"]
• Branch name: renovate/major-jest-monorepo
• Merge into: main
• Upgrade @jest/reporters to ^30.0.0
• Upgrade @jest/test-result to ^30.0.0
• Upgrade @jest/types to ^30.0.0
• Upgrade jest to ^30.0.0

Update nx monorepo to v21 (major)

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

Update opentelemetry-js monorepo to v2 (major)

• Schedule: ["at any time"]
• Branch name: renovate/major-opentelemetry-js-monorepo
• Merge into: main
• Upgrade @opentelemetry/core to ^2.0.0
• Upgrade @opentelemetry/resources to ^2.0.0
• Upgrade @opentelemetry/sdk-trace-base to ^2.0.0

Update typescript-eslint monorepo to v8 (major)

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

🚸 Branch 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.

[opentaco-cloud]

❌ Error loading digger config: error loading digger.yml: error cloning and loading config could not read the file both digger.yml and digger.yaml are missing: open /tmp/repo1254115530/digger.yaml: no such file or directory

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Join our Discord community for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore or @coderabbit ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.