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 - autoclosed #306

Closed
wants to merge 1 commit into from
Closed

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 8, 2024

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

  • docs/Gemfile (bundler)
  • cli/Cargo.toml (cargo)
  • lib/Cargo.toml (cargo)
  • xtask/Cargo.toml (cargo)
  • ci/Dockerfile.ci (dockerfile)
  • ci/Dockerfile.fcos (dockerfile)
  • hack/Containerfile (dockerfile)
  • .github/workflows/autovendor.yml (github-actions)
  • .github/workflows/ci.yml (github-actions)
  • .github/workflows/docs.yml (github-actions)
  • .github/workflows/labeler.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 31 Pull Requests:

fix(deps): update rust crate anstream to 0.6.11
  • Schedule: ["at any time"]
  • Branch name: renovate/anstream-0.x
  • Merge into: main
  • Upgrade anstream to 0.6.11
fix(deps): update rust crate anstyle to 1.0.6
  • Schedule: ["at any time"]
  • Branch name: renovate/anstyle-1.x
  • Merge into: main
  • Upgrade anstyle to 1.0.6
fix(deps): update rust crate anyhow to 1.0.79
  • Schedule: ["at any time"]
  • Branch name: renovate/anyhow-1.x
  • Merge into: main
  • Upgrade anyhow to 1.0.79
fix(deps): update rust crate chrono to 0.4.33
  • Schedule: ["at any time"]
  • Branch name: renovate/chrono-0.x
  • Merge into: main
  • Upgrade chrono to 0.4.33
fix(deps): update rust crate fn-error-context to 0.2.1
  • Schedule: ["at any time"]
  • Branch name: renovate/fn-error-context-0.x
  • Merge into: main
  • Upgrade fn-error-context to 0.2.1
fix(deps): update rust crate hex to ^0.4.3
  • Schedule: ["at any time"]
  • Branch name: renovate/hex-0.x
  • Merge into: main
  • Upgrade hex to ^0.4.3
fix(deps): update rust crate indicatif to 0.17.7
  • Schedule: ["at any time"]
  • Branch name: renovate/indicatif-0.x
  • Merge into: main
  • Upgrade indicatif to 0.17.7
fix(deps): update rust crate libc to v0.2.153
  • Schedule: ["at any time"]
  • Branch name: renovate/libc-0.x
  • Merge into: main
  • Upgrade libc to ^0.2.153
  • Upgrade libc to 0.2.153
fix(deps): update rust crate log to 0.4.20
  • Schedule: ["at any time"]
  • Branch name: renovate/log-0.x
  • Merge into: main
  • Upgrade log to 0.4.20
fix(deps): update rust crate openssl to ^0.10.63
  • Schedule: ["at any time"]
  • Branch name: renovate/openssl-0.x
  • Merge into: main
  • Upgrade openssl to ^0.10.63
fix(deps): update rust crate schemars to 0.8.16
  • Schedule: ["at any time"]
  • Branch name: renovate/schemars-0.x
  • Merge into: main
  • Upgrade schemars to 0.8.16
fix(deps): update rust crate serde to 1.0.196
  • Schedule: ["at any time"]
  • Branch name: renovate/serde-monorepo
  • Merge into: main
  • Upgrade serde to 1.0.196
fix(deps): update rust crate serde_ignored to 0.1.10
  • Schedule: ["at any time"]
  • Branch name: renovate/serde_ignored-0.x
  • Merge into: main
  • Upgrade serde_ignored to 0.1.10
fix(deps): update rust crate serde_json to 1.0.113
  • Schedule: ["at any time"]
  • Branch name: renovate/serde_json-1.x
  • Merge into: main
  • Upgrade serde_json to 1.0.113
fix(deps): update rust crate serde_yaml to 0.9.31
  • Schedule: ["at any time"]
  • Branch name: renovate/serde_yaml-0.x
  • Merge into: main
  • Upgrade serde_yaml to 0.9.31
fix(deps): update rust crate camino to v1.1.6
  • Schedule: ["at any time"]
  • Branch name: renovate/camino-1.x
  • Merge into: main
  • Upgrade camino to 1.1
  • Upgrade camino to 1.1.6
fix(deps): update rust crate clap to 4.5
  • Schedule: ["at any time"]
  • Branch name: renovate/clap-4.x
  • Merge into: main
  • Upgrade clap to 4.5
fix(deps): update rust crate gvariant to 0.5.0
  • Schedule: ["at any time"]
  • Branch name: renovate/gvariant-0.x
  • Merge into: main
  • Upgrade gvariant to 0.5.0
fix(deps): update rust crate once_cell to 1.19
  • Schedule: ["at any time"]
  • Branch name: renovate/once_cell-1.x
  • Merge into: main
  • Upgrade once_cell to 1.19
fix(deps): update rust crate regex to 1.10.3
  • Schedule: ["at any time"]
  • Branch name: renovate/regex-1.x
  • Merge into: main
  • Upgrade regex to 1.10.3
fix(deps): update rust crate tempfile to v3.10.0
  • Schedule: ["at any time"]
  • Branch name: renovate/tempfile-3.x
  • Merge into: main
  • Upgrade tempfile to 3.10
  • Upgrade tempfile to 3.10.0
fix(deps): update rust crate tokio to >= 1.36.0
  • Schedule: ["at any time"]
  • Branch name: renovate/tokio-1.x
  • Merge into: main
  • Upgrade tokio to >= 1.36.0
fix(deps): update rust crate toml to 0.8.10
  • Schedule: ["at any time"]
  • Branch name: renovate/toml-0.x
  • Merge into: main
  • Upgrade toml to 0.8.10
fix(deps): update rust crate uuid to 1.7.0
  • Schedule: ["at any time"]
  • Branch name: renovate/uuid-1.x
  • Merge into: main
  • Upgrade uuid to 1.7.0
chore(deps): update actions/checkout action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-4.x
  • Merge into: main
  • Upgrade actions/checkout to v4
chore(deps): update actions/configure-pages action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-configure-pages-4.x
  • Merge into: main
  • Upgrade actions/configure-pages to v4
chore(deps): update actions/deploy-pages action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-deploy-pages-4.x
  • Merge into: main
  • Upgrade actions/deploy-pages to v4
chore(deps): update actions/download-artifact action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-download-artifact-4.x
  • Merge into: main
  • Upgrade actions/download-artifact to v4
chore(deps): update actions/upload-artifact action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-upload-artifact-4.x
  • Merge into: main
  • Upgrade actions/upload-artifact to v4
chore(deps): update actions/upload-pages-artifact action to v3
fix(deps): update rust crate serde_with to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/serde_with-3.x
  • Merge into: main
  • Upgrade serde_with to >= 1.9.4, < 4

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

Copy link

openshift-ci bot commented Feb 8, 2024

Hi @renovate[bot]. Thanks for your PR.

I'm waiting for a containers member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@renovate renovate bot changed the title chore: Configure Renovate chore: Configure Renovate - autoclosed Feb 8, 2024
@renovate renovate bot closed this Feb 8, 2024
@renovate renovate bot deleted the renovate/configure branch February 8, 2024 20:52
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