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 #138

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

chore: Configure Renovate #138

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Nov 29, 2024

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

  • Gemfile (bundler)
  • docker-compose-verify.yml (docker-compose)
  • Dockerfile (dockerfile)
  • Dockerfile-bundle-base (dockerfile)
  • Dockerfile-node (dockerfile)
  • .github/workflows/audit.yml (github-actions)
  • .github/workflows/release_image.yml (github-actions)
  • .github/workflows/smartbear-issue-label-added.yml (github-actions)
  • .github/workflows/test.yml (github-actions)
  • .github/workflows/triage.yml (github-actions)
  • .github/workflows/update-gems.yml (github-actions)
  • .ruby-version (ruby-version)

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 (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 5 Pull Requests:

chore(deps): update alpine docker tag to v3.21
  • Schedule: ["at any time"]
  • Branch name: renovate/alpine-3.x
  • Merge into: master
  • Upgrade alpine to 3.21
chore(deps): update docker/login-action action to v3.3.0
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-login-action-3.x
  • Merge into: master
  • Upgrade docker/login-action to 9780b0c442fbb1117ed29e0efdff1e18412f7567
chore(deps): update ruby docker tag to v3.3
  • Schedule: ["at any time"]
  • Branch name: renovate/ruby-3.x
  • Merge into: master
  • Upgrade ruby to 3.3-alpine
chore(deps): update node.js to v22
  • Schedule: ["at any time"]
  • Branch name: renovate/node-22.x
  • Merge into: master
  • Upgrade node to 22-alpine3.20
chore(deps): update peter-evans/repository-dispatch action to v3

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

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

Successfully merging this pull request may close these issues.

0 participants