Configure Renovate #1
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/configure"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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).gitea/workflows/publish.yaml
(github-actions)package.json
(npm)Configuration Summary
Based on the default config's presets, Renovate will:
fix
for dependencies andchore
for all others if semantic commits are in use.node_modules
,bower_components
,vendor
and various test/tests directories.🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the
renovate.json
in this branch with your custom config and the list of Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs.What to Expect
With your current configuration, Renovate will create 3 Pull Requests:
fix(deps): update dependency dotenv to v16.3.1
renovate/dotenv-16.x-lockfile
master
16.3.1
chore(deps): update docker/build-push-action action to v5
renovate/docker-build-push-action-5.x
master
v5
fix(deps): update dependency prom-client to v15
renovate/prom-client-15.x
master
^15.0.0
🚸 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 has been generated by Renovate Bot.