Files
renovate-botandrmcampos deeea1d148
Build Deploy to Pages / build (push) Successful in 5m8s
chore: Configure Renovate (#1)
Welcome to [Renovate](https://github.com/renovatebot/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](https://docs.renovatebot.com/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

 * `package.json` (npm)

### Configuration Summary

Based on the default config's presets, Renovate will:

  - Start dependency updates only once this onboarding PR is merged
  - 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 7 Pull Requests:

<details>
<summary>chore(deps): update nextjs monorepo to v15.5.20</summary>

  - Schedule: ["at any time"]
  - Branch name: `renovate/nextjs-monorepo`
  - Merge into: `main`
  - Upgrade [eslint-config-next](https://github.com/vercel/next.js) to `15.5.20`
  - Upgrade [next](https://github.com/vercel/next.js) to `15.5.20`

</details>

<details>
<summary>chore(deps): update radix-ui-primitives monorepo</summary>

  - Schedule: ["at any time"]
  - Branch name: `renovate/radix-ui-primitives-monorepo`
  - Merge into: `main`
  - Upgrade [@radix-ui/react-dialog](https://github.com/radix-ui/primitives) to `1.1.18`
  - Upgrade [@radix-ui/react-radio-group](https://github.com/radix-ui/primitives) to `1.4.2`
  - Upgrade [@radix-ui/react-separator](https://github.com/radix-ui/primitives) to `1.1.11`

</details>

<details>
<summary>chore(deps): update tailwindcss monorepo to v4.3.2</summary>

  - Schedule: ["at any time"]
  - Branch name: `renovate/tailwindcss-monorepo`
  - Merge into: `main`
  - Upgrade [@tailwindcss/postcss](https://github.com/tailwindlabs/tailwindcss) to `4.3.2`
  - Upgrade [tailwindcss](https://github.com/tailwindlabs/tailwindcss) to `4.3.2`

</details>

<details>
<summary>chore(deps): update dependency eslint to v10</summary>

  - Schedule: ["at any time"]
  - Branch name: `renovate/major-eslint-monorepo`
  - Merge into: `main`
  - Upgrade [eslint](https://github.com/eslint/eslint) to `^10.0.0`

</details>

<details>
<summary>chore(deps): update dependency typescript to v6</summary>

  - Schedule: ["at any time"]
  - Branch name: `renovate/typescript-6.x`
  - Merge into: `main`
  - Upgrade [typescript](https://github.com/microsoft/TypeScript) to `^6.0.0`

</details>

<details>
<summary>fix(deps): update dependency lucide-react to v1</summary>

  - Schedule: ["at any time"]
  - Branch name: `renovate/major-lucide-monorepo`
  - Merge into: `main`
  - Upgrade [lucide-react](https://github.com/lucide-icons/lucide) to `^1.0.0`

</details>

<details>
<summary>fix(deps): update nextjs monorepo to v16</summary>

  - Schedule: ["at any time"]
  - Branch name: `renovate/major-nextjs-monorepo`
  - Merge into: `main`
  - Upgrade [eslint-config-next](https://github.com/vercel/next.js) to `^16.0.0`
  - Upgrade [next](https://github.com/vercel/next.js) to `^16.0.0`

</details>

🚸 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`](https://docs.renovatebot.com/configuration-options/#prhourlylimit) for details.

---

 Got questions? Check out Renovate's [Docs](https://docs.renovatebot.com/), particularly the Getting Started section.
If you need any further assistance then you can also [request help here](https://github.com/renovatebot/renovate/discussions).

---

This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate).

<!--renovate-config-hash:e80b4e42a3043bc12fa0640db4bac392d2bf770acf841360d7c8ceeeac2ec1a9-->

Reviewed-on: #1
Co-authored-by: Renovate Bot <renovate-bot@lightroasted.vps-kinghost.net>
Co-committed-by: Renovate Bot <renovate-bot@lightroasted.vps-kinghost.net>
2026-07-05 21:04:03 +00:00

7 lines
114 B
JSON

{
"$schema": "https://docs.renovatebot.com/renovate-schema.json",
"extends": [
"config:recommended"
]
}