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

• apps/biboumi/compose.yaml (docker-compose)
• apps/matterbridge/compose.yaml (docker-compose)
• compose.yaml (docker-compose)
• infra/turn-standalone/compose.yaml (docker-compose)
• apps/atheme/Containerfile (dockerfile)
• apps/gamja/Containerfile (dockerfile)
• apps/matterbridge/Containerfile (dockerfile)
• apps/prosody/Containerfile (dockerfile)
• apps/unrealircd/Containerfile (dockerfile)
• apps/webpanel/Containerfile (dockerfile)
• .github/workflows/ci.yml (github-actions)
• .github/workflows/docker.yml (github-actions)
• .github/workflows/lint.yml (github-actions)
• .github/workflows/security.yml (github-actions)
• apps/web/package.json (npm)
• package.json (npm)
• pnpm-workspace.yaml (npm)
• pyproject.toml (pep621)

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

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

chore(deps): update dependency next to v15 [security]

• Branch name: renovate/npm-next-vulnerability
• Merge into: main
• Upgrade next to 15.5.10

chore(deps): update alpine:3.23 docker digest to 2510918

• Schedule: ["at any time"]
• Branch name: renovate/alpine-3.23
• Merge into: main
• Upgrade alpine to sha256:25109184c71bdad752c8312a8623239686a9a2071e8825f20acb8f2198c3f659

chore(deps): update node.js to be0c5c5

• Schedule: ["at any time"]
• Branch name: renovate/node-current-alpine3.22
• Merge into: main
• Upgrade node to sha256:be0c5c5272d451d5faddfa4654495c530c51ab437b0d901a9c533d9635ad832a

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

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

chore(deps): update dependency @​types/react to v18.3.28

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

chore(deps): update dependency eslint-config-next to v14.2.35

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

chore(deps): update dependency tailwind-merge to v2.6.1

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

chore(deps): update pnpm to v9.15.9

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

chore(deps): update dependency @​biomejs/biome to v2.4.2

• Schedule: ["at any time"]
• Branch name: renovate/biomejs-biome-2.x
• Merge into: main
• Upgrade @biomejs/biome to 2.4.2

chore(deps): update dependency lucide-react to ^0.574.0

• Schedule: ["at any time"]
• Branch name: renovate/lucide-monorepo
• Merge into: main
• Upgrade lucide-react to ^0.574.0

chore(deps): update dependency ultracite to v7.2.3

• Schedule: ["at any time"]
• Branch name: renovate/ultracite-7.x
• Merge into: main
• Upgrade ultracite to 7.2.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 amir20/dozzle docker tag to v10

• Schedule: ["at any time"]
• Branch name: renovate/amir20-dozzle-10.x
• Merge into: main
• Upgrade amir20/dozzle to v10

chore(deps): update dependency eslint to v10

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

chore(deps): update dependency eslint-config-next to v16

• Schedule: ["at any time"]
• Branch name: renovate/major-nextjs-monorepo
• Merge into: main
• Upgrade eslint-config-next to 16.1.6

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 tailwind-merge to v3

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

chore(deps): update dependency tailwindcss to v4

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

chore(deps): update pnpm to v10

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

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

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

chore(deps): update react monorepo to v19 (major)

• Schedule: ["at any time"]
• Branch name: renovate/major-react-monorepo
• Merge into: main
• Upgrade @types/react to ^19.0.0
• Upgrade @types/react-dom to ^19.0.0
• Upgrade react to ^19.0.0
• Upgrade react-dom to ^19.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.

[sourcery-ai]

Reviewer's Guide

This PR bootstraps Renovate by adding a single renovate.json configuration file that applies default presets—enabling onboarding, scheduling, grouping, semantic commit types, ignore patterns, dashboards, and branch rate limits—to automate and streamline future dependency updates.

File-Level Changes

Change	Details	Files
Add Renovate configuration file with default presets	Introduce renovate.json at project root Enable onboarding PR and dependency dashboard Configure semantic commit types for fixes and chores Set ignore patterns for common directories Group monorepo and curated package sets Apply merge confidence badges and update schedules Limit branch creation to two per hour	renovate.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[cloudflare-workers-and-pages]

Deploying atl-chat with    Cloudflare Pages

Latest commit:	e697fb2
Status:	✅  Deploy successful!
Preview URL:	https://e46718c4.atl-chat.pages.dev
Branch Preview URL:	https://renovate-configure.atl-chat.pages.dev

View logs