Configure 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
-
docker-compose.yml(docker-compose) -
Dockerfile(dockerfile) -
.github/workflows/build.yml(github-actions) -
.github/workflows/test.yml(github-actions) -
server/package.json(npm)
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
fixfor dependencies andchorefor all others if semantic commits are in use. - Ignore
node_modules,bower_components,vendorand various test/tests (except for nuget) 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 docker/build-push-action action to v6
- Schedule: ["at any time"]
- Branch name:
renovate/docker-build-push-action-6.x - Merge into:
main - Upgrade docker/build-push-action to
v6
❓ 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.
⚠️ No Changeset found
Latest commit: a7901211f126329c7f0b8f014785298083411fcd
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