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.

---

Detected Package Files

• 1. Pub-sub/docker-compose.yml (docker-compose)
• 10. performance-comparison/1.consumer-single/docker-compose.yml (docker-compose)
• 10. performance-comparison/docker-compose.yml (docker-compose)
• 2. Publisher_confirm/1.sync-confirmation/docker-compose.yml (docker-compose)
• 2. Publisher_confirm/2.batch-confirmation/docker-compose.yml (docker-compose)
• 2. Publisher_confirm/3.async-confirmation/docker-compose.yml (docker-compose)
• 7.1. Delay_schedule_custom/consumer/docker-compose.yml (docker-compose)
• 7.1. Delay_schedule_custom/docker-compose.yml (docker-compose)
• 7.1. Delay_schedule_custom/publisher/docker-compose.yml (docker-compose)
• 7.2. Delay_schedule_custom_exponential_backoff/consumer/docker-compose.yml (docker-compose)
• 7.2. Delay_schedule_custom_exponential_backoff/docker-compose.yml (docker-compose)
• 7.2. Delay_schedule_custom_exponential_backoff/publisher/docker-compose.yml (docker-compose)
• 8. Event-based_microservices /docker-compose.yml (docker-compose)
• 9. clusterization/docker-compose.yml (docker-compose)
• 9. clusterization/external-publisher/docker-compose.yml (docker-compose)
• docker-compose.yml (docker-compose)
• 10. performance-comparison/1.consumer-single/Dockerfile (dockerfile)
• 2. Publisher_confirm/1.sync-confirmation/Dockerfile (dockerfile)
• 2. Publisher_confirm/2.batch-confirmation/Dockerfile (dockerfile)
• 2. Publisher_confirm/3.async-confirmation/Dockerfile (dockerfile)
• 7.1. Delay_schedule_custom/consumer/Dockerfile (dockerfile)
• 7.1. Delay_schedule_custom/publisher/Dockerfile (dockerfile)
• 7.2. Delay_schedule_custom_exponential_backoff/consumer/Dockerfile (dockerfile)
• 7.2. Delay_schedule_custom_exponential_backoff/publisher/Dockerfile (dockerfile)
• 8. Event-based_microservices /apps/gateway/Dockerfile (dockerfile)
• 8. Event-based_microservices /apps/service-stock/Dockerfile (dockerfile)
• 9. clusterization/external-publisher/Dockerfile (dockerfile)
• 1. Pub-sub/package.json (npm)
• 10. performance-comparison/package.json (npm)
• 2. Publisher_confirm/package.json (npm)
• 3. RPC/package.json (npm)
• 4. Alternate_exchange/package.json (npm)
• 5. Consistent_hash/package.json (npm)
• 6. DLX/package.json (npm)
• 7.1. Delay_schedule_custom/package.json (npm)
• 7.2. Delay_schedule_custom_exponential_backoff/package.json (npm)
• 7.3. Delay_schedule_plugin/package.json (npm)
• 8. Event-based_microservices /package.json (npm)
• 9. clusterization/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.

🔡 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 50 Pull Requests:

chore(deps): update dependency @​types/express to v4.17.23

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

chore(deps): update dependency @​types/node to v17.0.45

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

chore(deps): update dependency @​types/supertest to v2.0.16

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

chore(deps): update dependency eslint-config-prettier to v8.10.2

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

chore(deps): 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

chore(deps): update dependency eslint-plugin-prettier to v4.2.5

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

chore(deps): update dependency nodemon to v3.1.10

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

chore(deps): update dependency supertest to v6.3.4

• Schedule: ["at any time"]
• Branch name: renovate/supertest-6.x-lockfile
• Merge into: main
• Upgrade supertest to 6.3.4

chore(deps): update dependency ts-node to v10.9.2

• Schedule: ["at any time"]
• Branch name: renovate/ts-node-10.x-lockfile
• Merge into: main
• Upgrade ts-node to 10.9.2

chore(deps): update jest monorepo

• Schedule: ["at any time"]
• Branch name: renovate/jest-monorepo
• Merge into: main
• Upgrade @types/jest to 29.5.14
• Upgrade jest to 29.7.0

fix(deps): update dependency amqp-connection-manager to v4.1.14

• Schedule: ["at any time"]
• Branch name: renovate/amqp-connection-manager-4.x-lockfile
• Merge into: main
• Upgrade amqp-connection-manager to 4.1.14

fix(deps): update dependency amqplib to v0.10.8

• Schedule: ["at any time"]
• Branch name: renovate/amqplib-0.x-lockfile
• Merge into: main
• Upgrade amqplib to 0.10.8

fix(deps): update dependency rimraf to v5.0.10

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

fix(deps): update dependency rxjs to v7.8.2

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

fix(deps): update dependency uuid to v9.0.1

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

fix(deps): update nest monorepo to v9.4.3

• Schedule: ["at any time"]
• Branch name: renovate/nest-monorepo
• Merge into: main
• Upgrade @nestjs/common to 9.4.3
• Upgrade @nestjs/core to 9.4.3
• Upgrade @nestjs/microservices to 9.4.3
• Upgrade @nestjs/platform-express to 9.4.3
• Upgrade @nestjs/testing to 9.4.3

chore(deps): update dependency @​types/node to v20.19.9

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

chore(deps): 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

chore(deps): update dependency eslint-config-prettier to v8.10.2

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

chore(deps): 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

chore(deps): update dependency ts-jest to v29.4.0

• Schedule: ["at any time"]
• Branch name: renovate/ts-jest-29.x-lockfile
• Merge into: main
• Upgrade ts-jest to 29.4.0

chore(deps): update dependency ts-loader to v9.5.2

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

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

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

chore(deps): update dependency typescript to v5.8.3

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

chore(deps): update haproxy docker tag to v2.9.15

• Schedule: ["at any time"]
• Branch name: renovate/haproxy-2.x
• Merge into: main
• Upgrade haproxy to 2.9.15-alpine

chore(deps): update typescript-eslint monorepo to v5.62.0

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

fix(deps): update dependency @​golevelup/nestjs-rabbitmq to v3.7.0

• Schedule: ["at any time"]
• Branch name: renovate/golevelup-nestjs-rabbitmq-3.x-lockfile
• Merge into: main
• Upgrade @golevelup/nestjs-rabbitmq to 3.7.0

fix(deps): update dependency amqplib to ^0.10.0

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

fix(deps): update dependency mongoose to v7.8.7

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

fix(deps): update dependency reflect-metadata to ^0.2.0

• Schedule: ["at any time"]
• Branch name: renovate/reflect-metadata-0.x
• Merge into: main
• Upgrade reflect-metadata to ^0.2.0

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

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

chore(deps): update dependency @​types/supertest to v6

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

chore(deps): update dependency dotenv-cli to v9

• Schedule: ["at any time"]
• Branch name: renovate/dotenv-cli-9.x
• Merge into: main
• Upgrade dotenv-cli to ^9.0.0

chore(deps): update dependency eslint to v9

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

chore(deps): 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
• Upgrade eslint-config-prettier to 10.1.8

chore(deps): 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

chore(deps): update dependency eslint-plugin-prettier to v5

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

chore(deps): update dependency prettier to v3

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

chore(deps): update dependency supertest to v7

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

chore(deps): update haproxy docker tag to v3

• Schedule: ["at any time"]
• Branch name: renovate/haproxy-3.x
• Merge into: main
• Upgrade haproxy to 3.2.3-alpine

chore(deps): update jest monorepo to v30 (major)

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

chore(deps): update rabbitmq docker tag to v4

• Schedule: ["at any time"]
• Branch name: renovate/rabbitmq-4.x
• Merge into: main
• Upgrade rabbitmq to 4-management-alpine
• Upgrade rabbitmq to 4-management

chore(deps): 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

fix(deps): update dependency @​golevelup/nestjs-rabbitmq to v6

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

fix(deps): update dependency express to v5

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

fix(deps): update dependency mongoose to v8

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

fix(deps): update dependency rimraf to v6

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

fix(deps): update dependency uuid to v11

• Schedule: ["at any time"]
• Branch name: renovate/uuid-11.x
• Merge into: main
• Upgrade uuid to ^11.0.0

fix(deps): update dependency yargs to v18

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

fix(deps): update nest monorepo to v11 (major)

• Schedule: ["at any time"]
• Branch name: renovate/major-nest-monorepo
• Merge into: main
• Upgrade @nestjs/cli to ^11.0.0
• Upgrade @nestjs/common to ^11.0.0
• Upgrade @nestjs/core to ^11.0.0
• Upgrade @nestjs/microservices to ^11.0.0
• Upgrade @nestjs/platform-express to ^11.0.0
• Upgrade @nestjs/schematics to ^11.0.0
• Upgrade @nestjs/testing to ^11.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.

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

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • Generate unit testing code for this file.
  • 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. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• 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 src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai 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

Documentation and Community

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