8000 Configure Renovate by renovate[bot] · Pull Request #1 · ZentriaMC/journalsql · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Configure Renovate #1

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.

Sign up for GitHub

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

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

Configure Renovate #1

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
@renovate renovate bot commented May 28, 2023 •
edited
Loading

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)
  • journalsqld/Cargo.toml (cargo)
  • parser/Cargo.toml (cargo)

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

Update Rust crate anyhow to v1.0.94
  • Schedule: ["at any time"]
  • Branch name: renovate/anyhow-1.x-lockfile
  • Merge into: master
  • Upgrade anyhow to 1.0.94
Update Rust crate log to v0.4.22
  • Schedule: ["at any time"]
  • Branch name: renovate/log-0.x-lockfile
  • Merge into: master
  • Upgrade log to 0.4.22
Update Rust crate prometheus to v0.13.4
  • Schedule: ["at any time"]
  • Branch name: renovate/prometheus-0.x-lockfile
  • Merge into: master
  • Upgrade prometheus to 0.13.4
Update Rust crate serde to v1.0.216
  • Schedule: ["at any time"]
  • Branch name: renovate/serde-monorepo
  • Merge into: master
  • Upgrade serde to 1.0.216
Update Rust crate serde_json to v1.0.133
  • Schedule: ["at any time"]
  • Branch name: renovate/serde_json-1.x-lockfile
  • Merge into: master
  • Upgrade serde_json to 1.0.133
Update Rust crate signal-hook to v0.3.17
  • Schedule: ["at any time"]
  • Branch name: renovate/signal-hook-0.x-lockfile
  • Merge into: master
  • Upgrade signal-hook to 0.3.17
Update Rust crate thiserror to v1.0.69
  • Schedule: ["at any time"]
  • Branch name: renovate/thiserror-1.x-lockfile
  • Merge into: master
  • Upgrade thiserror to 1.0.69
Update Rust crate time to v0.3.37
  • Schedule: ["at any time"]
  • Branch name: renovate/time-0.x-lockfile
  • Merge into: master
  • Upgrade time to 0.3.37
Update Rust crate url to v2.5.4
  • Schedule: ["at any time"]
  • Branch name: renovate/url-2.x-lockfile
  • Merge into: master
  • Upgrade url to 2.5.4
Update Rust crate base64 to 0.22.0
  • Schedule: ["at any time"]
  • Branch name: renovate/base64-0.x
  • Merge into: master
  • Upgrade base64 to 0.22.0
Update Rust crate clickhouse to 0.13.0
  • Schedule: ["at any time"]
  • Branch name: renovate/clickhouse-0.x
  • Merge into: master
  • Upgrade clickhouse to 0.13.0
Update Rust crate env_logger to 0.11
  • Schedule: ["at any time"]
  • Branch name: renovate/env_logger-0.x
  • Merge into: master
  • Upgrade env_logger to 0.11
Update Rust crate lazy_static to v1.5.0
  • Schedule: ["at any time"]
  • Branch name: renovate/lazy_static-1.x-lockfile
  • Merge into: master
  • Upgrade lazy_static to 1.5.0
Update Rust crate num_cpus to v1.16.0
  • Schedule: ["at any time"]
  • Branch name: renovate/num_cpus-1.x-lockfile
  • Merge into: master
  • Upgrade num_cpus to 1.16.0
Update Rust crate strum to 0.26
  • Schedule: ["at any time"]
  • Branch name: renovate/strum-monorepo
  • Merge into: master
  • Upgrade strum to 0.26
Update Rust crate tokio to v1.42.0
  • Schedule: ["at any time"]
  • Branch name: renovate/tokio-1.x-lockfile
  • Merge into: master
  • Upgrade tokio to 1.42.0
Update Rust crate thiserror to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/thiserror-2.x
  • Merge into: master
  • Upgrade thiserror to 2.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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/configure branch from 1e0efd1 to 4a4e60e Compare December 4, 2023 05:51
@renovate renovate bot force-pushed the renovate/configure branch from 4a4e60e to fe0675c Compare December 15, 2023 02:41
@renovate renovate bot force-pushed the renovate/configure branch from fe0675c to 6f5ce4e Compare December 11, 2024 23:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants
0