chore: Configure Renovate

renovate[bot] commented 2 months ago

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

.github/workflows/checks.yml (github-actions)
go.mod (gomod)

Configuration Summary

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

Start dependency updates only once this onboarding PR is merged
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 directories.
Group known monorepo packages together.
Use curated list of recommended non-monorepo package groupings.
Apply crowd-sourced package replacement rules.
Apply crowd-sourced workarounds for known problems with packages.

🔡 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 1 Pull Request:

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

- Schedule: ["at any time"] - Branch name: `renovate/actions-checkout-4.x` - Merge into: `main` - Upgrade [actions/checkout](https://togithub.com/actions/checkout) to `v4`

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

stackblitz[bot] commented 2 months ago

Run & review this pull request in StackBlitz Codeflow.

changeset-bot[bot] commented 2 months ago

⚠️ No Changeset found

Latest commit: 575560b1eb34a8aff122bf1fa58fa0ba54c433c7

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

capytal / dislate