chore: Configure Renovate (#5)

Welcome to [Renovate](https://redirect.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

 * `.github/workflows/ci.yml` (github-actions)
 * `.github/workflows/deploy.yml` (github-actions)
 * `.github/workflows/links.yml` (github-actions)
 * `pyproject.toml` (pep621)
 * `terragrunt/terragrunt.hcl` (terragrunt)

### 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

---

### What to Expect

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

<details>
<summary>chore(deps): update actions/cache action to v5</summary>

  - Schedule: ["at any time"]
  - Branch name: `renovate/actions-cache-5.x`
  - Merge into: `main`
- Upgrade [actions/cache](https://redirect.github.com/actions/cache) to
`v5`


</details>

<details>
<summary>chore(deps): update actions/checkout action to v6</summary>

  - Schedule: ["at any time"]
  - Branch name: `renovate/actions-checkout-6.x`
  - Merge into: `main`
- Upgrade
[actions/checkout](https://redirect.github.com/actions/checkout) to `v6`


</details>

<details>
<summary>chore(deps): update actions/configure-pages action to
v6</summary>

  - Schedule: ["at any time"]
  - Branch name: `renovate/actions-configure-pages-6.x`
  - Merge into: `main`
- Upgrade
[actions/configure-pages](https://redirect.github.com/actions/configure-pages)
to `v6`


</details>

<details>
<summary>chore(deps): update actions/deploy-pages action to v5</summary>

  - Schedule: ["at any time"]
  - Branch name: `renovate/actions-deploy-pages-5.x`
  - Merge into: `main`
- Upgrade
[actions/deploy-pages](https://redirect.github.com/actions/deploy-pages)
to `v5`


</details>

<details>
<summary>chore(deps): update actions/upload-pages-artifact action to
v5</summary>

  - Schedule: ["at any time"]
  - Branch name: `renovate/actions-upload-pages-artifact-5.x`
  - Merge into: `main`
- Upgrade
[actions/upload-pages-artifact](https://redirect.github.com/actions/upload-pages-artifact)
to `v5`


</details>

<details>
<summary>chore(deps): update astral-sh/setup-uv action to v8</summary>

  - Schedule: ["at any time"]
  - Branch name: `renovate/astral-sh-setup-uv-8.x`
  - Merge into: `main`
- Upgrade
[astral-sh/setup-uv](https://redirect.github.com/astral-sh/setup-uv) to
`v8.1.0`


</details>

<details>
<summary>chore(deps): update peter-evans/create-issue-from-file action
to v6</summary>

  - Schedule: ["at any time"]
  - Branch name: `renovate/peter-evans-create-issue-from-file-6.x`
  - Merge into: `main`
- Upgrade
[peter-evans/create-issue-from-file](https://redirect.github.com/peter-evans/create-issue-from-file)
to `v6`


</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://redirect.github.com/renovatebot/renovate/discussions).


---

This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/RemoteRabbit/boilplate).


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

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Tristan Jahnke <trjahnke@protonmail.com>

Author: renovate[bot]

renovate.json

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