Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Configure Renovate #51

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

doctolib-renovate[bot]
Copy link

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

  • load_test/Dockerfile (dockerfile)
  • neurow/Dockerfile (dockerfile)
  • .github/workflows/ci.yml (github-actions)
  • .github/workflows/docker_push.yml (github-actions)
  • load_test/mix.exs (mix)
  • neurow/mix.exs (mix)
  • load_test/terraform/providers.tf (terraform)

Configuration Summary

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

  • Start dependency updates only once this onboarding PR is merged
  • 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.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.
  • Pin Docker digests.
  • Pin github-action digests.
  • Disable Renovate Dependency Dashboard creation.
  • Update base OS in Dockerfiles
  • Update Helm chart export custom format
  • Update external groups
  • Update GitHub Actions according to our policy
  • Update internal (Doctolib-owned) groups
  • Remap log levels
  • Update runtimes in group

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

chore(deps): pin dependencies
  • Schedule: ["at any time"]
  • Branch name: renovate/pin-dependencies
  • Merge into: main
  • Upgrade actions/checkout to 11bd71901bbe5b1630ceea73d27597364c9af683
  • Upgrade elixir to sha256:d61305d4da825b3fcd4248dba5ad263424774c9d8865ab164b1b0394e5fb7e1e
chore(deps): update dependency observer_cli to v1.8.2
  • Schedule: ["at any time"]
  • Branch name: renovate/observer_cli-1.x-lockfile
  • Merge into: main
  • Upgrade observer_cli to 1.8.2
chore(deps): update dependency plug_cowboy to v2.7.2
  • Schedule: ["at any time"]
  • Branch name: renovate/plug_cowboy-2.x-lockfile
  • Merge into: main
  • Upgrade plug_cowboy to 2.7.2
chore(deps): update dependency finch to ~> 0.19
  • Schedule: ["at any time"]
  • Branch name: renovate/finch-0.x
  • Merge into: main
  • Upgrade finch to ~> 0.19
chore(deps): update dependency libcluster to v3.5.0
  • Schedule: ["at any time"]
  • Branch name: renovate/libcluster-3.x-lockfile
  • Merge into: main
  • Upgrade libcluster to 3.5.0
chore(deps): lock file maintenance
  • Schedule: ["before 4am on monday"]
  • Branch name: renovate/lock-file-maintenance
  • Merge into: main
  • Regenerate lock files to use latest dependency versions

❓ 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 created by Renovate.

Details

Check the default configuration and documentation.

This PR was created during this run (see the logs on Datadog).
To replay this update, you can use the following packageRules on the Manual Run page: [{"matchPackageNames": ["*"], "enabled": false}, {"matchPackageNames": [""], "enabled": true}]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants