elastic / package-registry

Elastic Package Registry (EPR)
Other
40 stars 66 forks source link

Configure Renovate #1201

Closed elastic-renovate-prod[bot] closed 1 month ago

elastic-renovate-prod[bot] commented 1 month ago

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

Configuration Summary

Based on the default config's presets, Renovate will:

🔡 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:

Pin dependencies - Schedule: ["at any time"] - Branch name: `renovate/pin-dependencies` - Merge into: `main` - Upgrade cgr.dev/chainguard/wolfi-base to `sha256:1c7fcbc7d67145b82f8d393eabf43cf12a14e3759f2e42c8cb61799550909a08` - Upgrade docker.elastic.co/package-registry/package-registry to `sha256:54e8c1e2032bd91007d15346d978f616ff6b73b098f82dfb84fb8bedc554a805` - Upgrade golang to `sha256:2bd56f00ff47baf33e64eae7996b65846c7cb5e0a46e0a882ef179fd89654afa`
Update buildkite plugin junit-annotate to v2.5.0 - Schedule: ["at any time"] - Branch name: `renovate/junit-annotate-2.x` - Merge into: `main` - Upgrade [junit-annotate](https://togithub.com/buildkite-plugins/junit-annotate-buildkite-plugin) to `v2.5.0`
Update docker.elastic.co/package-registry/package-registry Docker tag to v0.21.0 - Schedule: ["at any time"] - Branch name: `renovate/docker.elastic.co-package-registry-package-registry-0.x` - Merge into: `main` - Upgrade docker.elastic.co/package-registry/package-registry to `sha256:e86d5448deb0347e914ae0e6f10fc605710ff0dd0b465b682894bc6c3bee7caa`
Update docker.elastic.co/package-registry/package-registry Docker tag to v1 - Schedule: ["at any time"] - Branch name: `renovate/docker.elastic.co-package-registry-package-registry-1.x` - Merge into: `main` - Upgrade docker.elastic.co/package-registry/package-registry to `sha256:7385f3e063b20f7c330f6d9bd1db2cf39248c8e653dfea0d58fd180486c665ff`
Update module gopkg.in/yaml.v2 to v3 - Schedule: ["at any time"] - Branch name: `renovate/gopkg.in-yaml.v2-3.x` - Merge into: `main` - Upgrade [gopkg.in/yaml.v2](https://togithub.com/go-yaml/yaml) to `v3.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 Renovate Bot.

rowlandgeoff commented 1 month ago

Closing for now. We will evaluate as part of https://github.com/elastic/ingest-dev/issues/3769.

elastic-renovate-prod[bot] commented 1 month ago

Renovate is disabled

Renovate is disabled because there is no Renovate configuration file. To enable Renovate, you can either (a) change this PR's title to get a new onboarding PR, and merge the new onboarding PR, or (b) create a Renovate config file, and commit that file to your base branch.