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

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

Configure Renovate #1

wants to merge 1 commit into from

Conversation

hutao-bot[bot]
Copy link

@hutao-bot hutao-bot bot commented Oct 4, 2023

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

  • package.json (bun)
  • Dockerfile (dockerfile)
  • .github/workflows/docker-publish.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 8 Pull Requests:

Update dependency @​kubernetes/client-node to ^0.21.0
  • Schedule: ["at any time"]
  • Branch name: renovate/kubernetes-client-node-0.x
  • Merge into: main
  • Upgrade @kubernetes/client-node to ^0.21.0
Update docker/build-push-action action to v5.4.0
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-build-push-action-5.x
  • Merge into: main
  • Upgrade docker/build-push-action to ca052bb54ab0790a636c9b5f226502c73d547a25
Update docker/login-action action to v3.3.0
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-login-action-3.x
  • Merge into: main
  • Upgrade docker/login-action to 9780b0c442fbb1117ed29e0efdff1e18412f7567
Update docker/metadata-action action to v5.5.1
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-metadata-action-5.x
  • Merge into: main
  • Upgrade docker/metadata-action to 8e5442c4ef9f78752691e2d8f8d19755c6f78e81
Update docker/setup-buildx-action action to v3.6.1
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-setup-buildx-action-3.x
  • Merge into: main
  • Upgrade docker/setup-buildx-action to 988b5a0280414f521da01fcc63a27aeeb4b104db
Update sigstore/cosign-installer action to v3.6.0
  • Schedule: ["at any time"]
  • Branch name: renovate/sigstore-cosign-installer-3.x
  • Merge into: main
  • Upgrade sigstore/cosign-installer to 4959ce089c160fddf62f7b42464195ba1a56d382
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
Update docker/build-push-action action to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-build-push-action-6.x
  • Merge into: main
  • Upgrade docker/build-push-action to 16ebe778df0e7752d2cfcbd924afdbbd89c1a755

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

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.

None yet

0 participants