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

Configure Renovate #5

Merged
merged 2 commits into from
Dec 29, 2023
Merged

Configure Renovate #5

merged 2 commits into from
Dec 29, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 1, 2023

Mend 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

  • Cargo.toml (cargo)
  • .github/workflows/build-release.yml (github-actions)
  • .github/workflows/ci-cargo-audit.yml (github-actions)
  • .github/workflows/ci-pr.yml (github-actions)
  • .github/workflows/ci-tags.yml (github-actions)
  • .github/workflows/clippy.yml (github-actions)
  • .github/workflows/create-release.yml (github-actions)
  • .github/workflows/trigger-workflow-in-other-repo.yml (github-actions)
  • .github/workflows/unit-tests.yml (github-actions)

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

Update Rust crate anyhow to 1.0.77
  • Schedule: ["at any time"]
  • Branch name: renovate/anyhow-1.x
  • Merge into: main
  • Upgrade anyhow to 1.0.77
Update Rust crate clap to 3.2.25
  • Schedule: ["at any time"]
  • Branch name: renovate/clap-3.x
  • Merge into: main
  • Upgrade clap to 3.2.25
Update Rust crate enigo to 0.1.3
  • Schedule: ["at any time"]
  • Branch name: renovate/enigo-0.x
  • Merge into: main
  • Upgrade enigo to 0.1.3
Update Rust crate clap to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/clap-4.x
  • Merge into: main
  • Upgrade clap to 4.4.12
Update Rust crate dirs to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/dirs-5.x
  • Merge into: main
  • Upgrade dirs to 5.0.1

🚸 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 Mend Renovate. View repository job log here.

@mdpadberg mdpadberg linked an issue Dec 1, 2023 that may be closed by this pull request
@mdpadberg mdpadberg merged commit bd576d1 into main Dec 29, 2023
1 of 4 checks passed
@mdpadberg mdpadberg deleted the renovate/configure branch December 29, 2023 22:11
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.

Renovate
1 participant