[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

• docker-compose.ci.yml (docker-compose)
• docker-compose.yml (docker-compose)
• bot/Dockerfile (dockerfile)
• .github/workflows/ci.yml (github-actions)
• bot/package.json (npm)
• 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 17 Pull Requests:

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

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

chore(deps): update dependency express to v4.22.2

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

chore(deps): update dependency mineflayer to v4.37.1

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

chore(deps): update dependency pg to v8.21.0

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

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

chore(deps): update oryd/kratos docker tag to v1.3.1

• Schedule: ["at any time"]
• Branch name: renovate/oryd-kratos-1.x
• Merge into: main
• Upgrade oryd/kratos to v1.3.1

fix(deps): update dependency @​takaro/apiclient to v0.7.3

• Schedule: ["at any time"]
• Branch name: renovate/takaro-apiclient-0.x
• Merge into: main
• Upgrade @​takaro/apiclient to 0.7.3

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

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

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

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

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 node to 24-alpine
• Upgrade @types/node to ^24.0.0

chore(deps): update dependency typescript to v6

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

chore(deps): update github artifact actions to v7

• Schedule: ["at any time"]
• Branch name: renovate/major-github-artifact-actions
• Merge into: main
• Upgrade actions/upload-artifact to v7

chore(deps): update oryd/kratos docker tag to v26

• Schedule: ["at any time"]
• Branch name: renovate/oryd-kratos-26.x
• Merge into: main
• Upgrade oryd/kratos to v26.2.0

chore(deps): update postgres docker tag to v18

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

chore(deps): update redis docker tag to v8

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

fix(deps): update dependency dotenv to v17

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

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

---

Warning

Please correct - or verify that you can safely ignore - these dependency lookup failures before you merge this PR.

• Failed to look up npm package @takaro/config: no-result
• Failed to look up npm package @takaro/db: no-result
• Failed to look up npm package @takaro/gameserver: no-result
• Failed to look up npm package @takaro/http: no-result
• Failed to look up npm package @takaro/mock-gameserver: no-result
• Failed to look up npm package @takaro/modules: no-result
• Failed to look up npm package @takaro/util: no-result

Files affected: package.json

---

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

---

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
• 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 explain its main purpose.
  • @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 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 sequence diagram to generate a sequence diagram of the changes in this PR.
• @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.

[niekcandaele]

Closing: the repository does not use Renovate. Dependencies are maintained by the Takaro team as part of the Official Registry. Superseded by the cleanup in #70.