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

renovate[bot]
Copy link

@renovate renovate bot commented Nov 8, 2022

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

  • cluster/Dockerfile (dockerfile)
  • cluster/images/provider-natssecrets-controller/Dockerfile (dockerfile)
  • cluster/images/provider-natssecrets/Dockerfile (dockerfile)
  • .github/workflows/backport.yml (github-actions)
  • .github/workflows/ci.yml (github-actions)
  • .github/workflows/codeql.yml (github-actions)
  • .github/workflows/commands.yml (github-actions)
  • .github/workflows/promote.yml (github-actions)
  • .github/workflows/tag.yml (github-actions)
  • go.mod (gomod)

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

fix(deps): update module github.com/crossplane/crossplane-runtime to v0.19.2 [security]
fix(deps): update github.com/crossplane/crossplane-tools digest to 628280f
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-crossplane-crossplane-tools-digest
  • Merge into: main
  • Upgrade github.com/crossplane/crossplane-tools to 628280f8bf79aae9e79d4b9ba596eb1f26221117
chore(deps): update zeebe-io/backport-action action to v0.0.9
  • Schedule: ["at any time"]
  • Branch name: renovate/zeebe-io-backport-action-0.x
  • Merge into: main
  • Upgrade zeebe-io/backport-action to v0.0.9
chore(deps): update alpine docker tag to v3.19
  • Schedule: ["at any time"]
  • Branch name: renovate/alpine-3.x
  • Merge into: main
  • Upgrade alpine to 3.19
chore(deps): update fkirc/skip-duplicate-actions action to v5.3.1
  • Schedule: ["at any time"]
  • Branch name: renovate/fkirc-skip-duplicate-actions-5.x
  • Merge into: main
  • Upgrade fkirc/skip-duplicate-actions to v5.3.1
chore(deps): update golang docker tag to v1.22
  • Schedule: ["at any time"]
  • Branch name: renovate/golang-1.x
  • Merge into: main
  • Upgrade golang to 1.22
fix(deps): update kubernetes packages to v0.29.3
fix(deps): update module github.com/edgefarm/vault-plugin-secrets-nats to v1.4.0
fix(deps): update module github.com/go-test/deep to v1.1.0
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-go-test-deep-1.x
  • Merge into: main
  • Upgrade github.com/go-test/deep to v1.1.0
fix(deps): update module github.com/google/go-cmp to v0.6.0
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-google-go-cmp-0.x
  • Merge into: main
  • Upgrade github.com/google/go-cmp to v0.6.0
fix(deps): update module github.com/hashicorp/vault/api to v1.12.2
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-hashicorp-vault-api-1.x
  • Merge into: main
  • Upgrade github.com/hashicorp/vault/api to v1.12.2
fix(deps): update module github.com/hashicorp/vault/sdk to v0.11.1
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-hashicorp-vault-sdk-0.x
  • Merge into: main
  • Upgrade github.com/hashicorp/vault/sdk to v0.11.1
fix(deps): update module gopkg.in/alecthomas/kingpin.v2 to v2.4.0
  • Schedule: ["at any time"]
  • Branch name: renovate/gopkg.in-alecthomas-kingpin.v2-2.x
  • Merge into: main
  • Upgrade gopkg.in/alecthomas/kingpin.v2 to v2.4.0
fix(deps): update module sigs.k8s.io/controller-runtime to v0.17.2
  • Schedule: ["at any time"]
  • Branch name: renovate/sigs.k8s.io-controller-runtime-0.x
  • Merge into: main
  • Upgrade sigs.k8s.io/controller-runtime to v0.17.2
fix(deps): update module sigs.k8s.io/controller-tools to v0.14.0
  • Schedule: ["at any time"]
  • Branch name: renovate/sigs.k8s.io-controller-tools-0.x
  • Merge into: main
  • Upgrade sigs.k8s.io/controller-tools to v0.14.0
chore(deps): update actions/cache action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-cache-4.x
  • Merge into: main
  • Upgrade actions/cache to v4
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/github-script action to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-github-script-7.x
  • Merge into: main
  • Upgrade actions/github-script to v7
chore(deps): update actions/setup-go action to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-setup-go-5.x
  • Merge into: main
  • Upgrade actions/setup-go to v5
chore(deps): update actions/upload-artifact action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/major-github-artifact-actions
  • Merge into: main
  • Upgrade actions/upload-artifact to v4
chore(deps): update codecov/codecov-action action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/codecov-codecov-action-4.x
  • Merge into: main
  • Upgrade codecov/codecov-action to v4
chore(deps): update docker/login-action action to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-login-action-3.x
  • Merge into: main
  • Upgrade docker/login-action to v3
chore(deps): update docker/setup-buildx-action action to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-setup-buildx-action-3.x
  • Merge into: main
  • Upgrade docker/setup-buildx-action to v3
chore(deps): update docker/setup-qemu-action action to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-setup-qemu-action-3.x
  • Merge into: main
  • Upgrade docker/setup-qemu-action to v3
chore(deps): update github/codeql-action action to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/github-codeql-action-3.x
  • Merge into: main
  • Upgrade github/codeql-action to v3
chore(deps): update golangci/golangci-lint-action action to v4
chore(deps): update xt0rted/slash-command-action action to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/xt0rted-slash-command-action-2.x
  • Merge into: main
  • Upgrade xt0rted/slash-command-action to v2
chore(deps): update zeebe-io/backport-action action to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/zeebe-io-backport-action-2.x
  • Merge into: main
  • Upgrade zeebe-io/backport-action to v2.4.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.

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