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

• template/.github/actions/deploy/action.yml (github-actions)
• template/.github/actions/setup-application/action.yml (github-actions)
• template/.github/actions/setup-nix/action.yml (github-actions)
• template/.github/actions/setup-php/action.yml (github-actions)
• template/.github/workflows/build-check.yml (github-actions)
• template/.github/workflows/playwright.yml (github-actions)
• renovate.json (renovate-config-presets)
• template/biome.json (jsonata)
• template/biome.json (jsonata)

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 not separate patch and minor upgrades into separate PRs for the same dependency.
• Rebase existing PRs any time the base branch has been updated.
• Add the renovate/ prefix to all branch names.
• Use semantic prefixes for commit messages and PR titles.
• Use semantic commit scope deps for all commits and PR titles.
• Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
• Update $schema version in biome.json configuration files.
• Group various lint packages together.
• Schedule automerge daily before 4 AM.
• Weekly schedule on early Monday mornings (before 4 AM).
• Schedule for weekends.
• Group PostCSS packages together.
• 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 not separate patch and minor upgrades into separate PRs for the same dependency.
• Rebase existing PRs any time the base branch has been updated.
• Add the renovate/ prefix to all branch names.
• Use semantic prefixes for commit messages and PR titles.
• Use semantic commit scope deps for all commits and PR titles.
• Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
• Update $schema version in biome.json configuration files.
• Group various lint packages together.
• Schedule automerge daily before 4 AM.
• Weekly schedule on early Monday mornings (before 4 AM).
• Schedule for weekends.
• Group PHP Illuminate packages together.
• Group PHPStan packages together.
• Run Renovate on following schedule: * * * * 0,6

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

chore(deps): update burnett01/rsync-deployments action to v7.1.0

• Schedule: ["* * * * 0,6"]
• Branch name: renovate/burnett01-rsync-deployments-7.x
• Merge into: main
• Upgrade burnett01/rsync-deployments to 7.1.0

chore(deps): update actions/cache action to v5

• Schedule: ["* * * * 0,6"]
• Branch name: renovate/actions-cache-5.x
• Merge into: main
• Upgrade actions/cache to v5

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

• Schedule: ["* * * * 0,6"]
• Branch name: renovate/actions-checkout-6.x
• Merge into: main
• Upgrade actions/checkout to v6

chore(deps): update actions/create-github-app-token action to v2

• Schedule: ["* * * * 0,6"]
• Branch name: renovate/actions-create-github-app-token-2.x
• Merge into: main
• Upgrade actions/create-github-app-token to v2

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

• Schedule: ["* * * * 0,6"]
• Branch name: renovate/actions-setup-node-6.x
• Merge into: main
• Upgrade actions/setup-node to v6

chore(deps): update actions/upload-artifact action to v6

• Schedule: ["* * * * 0,6"]
• Branch name: renovate/major-github-artifact-actions
• Merge into: main
• Upgrade actions/upload-artifact to v6

chore(deps): update burnett01/rsync-deployments action to v8

• Schedule: ["* * * * 0,6"]
• Branch name: renovate/burnett01-rsync-deployments-8.x
• Merge into: main
• Upgrade burnett01/rsync-deployments to 8.0.2

chore(deps): update cachix/cachix-action action to v16

• Schedule: ["* * * * 0,6"]
• Branch name: renovate/cachix-cachix-action-16.x
• Merge into: main
• Upgrade cachix/cachix-action to v16

chore(deps): update cachix/install-nix-action action to v31

• Schedule: ["* * * * 0,6"]
• Branch name: renovate/cachix-install-nix-action-31.x
• Merge into: main
• Upgrade cachix/install-nix-action to v31

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

• Schedule: ["* * * * 0,6"]
• Branch name: renovate/biomejs-biome-2.x
• Merge into: main
• Upgrade @biomejs/biome to 2.3.10

chore(deps): update determinatesystems/magic-nix-cache-action action to v13

• Schedule: ["* * * * 0,6"]
• Branch name: renovate/determinatesystems-magic-nix-cache-action-13.x
• Merge into: main
• Upgrade DeterminateSystems/magic-nix-cache-action to v13

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