Skip to content

chore: Configure Renovate#10

Open
elastic-renovate-prod[bot] wants to merge 1 commit intomainfrom
renovate/configure
Open

chore: Configure Renovate#10
elastic-renovate-prod[bot] wants to merge 1 commit intomainfrom
renovate/configure

Conversation

@elastic-renovate-prod
Copy link
Copy Markdown

@elastic-renovate-prod elastic-renovate-prod bot commented Mar 23, 2026

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

  • elastic/skills/elasticsearch/elasticsearch-esql/package.json (npm)
  • elastic/skills/elasticsearch/elasticsearch-file-ingest/package.json (npm)
  • elastic/skills/kibana/kibana-dashboards/package.json (npm)
  • elastic/skills/kibana/kibana-vega/package.json (npm)

Configuration Summary

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

  • Start dependency updates only once this onboarding PR is merged
  • Capture APK packages provided by Chainguard (https://ela.st/wolfi)
  • Capture packages annotated with # renovate: datasource=... depName=... headers; via https://renovate-docs.elastic.dev/modules/manager/dockerfile/
  • Renovate configuration to manage containers in docker.elastic.co/ci-agent-images/*. This is included by default and doesn't need to be explicitly pulled in
  • Group Chainguard packages, including Wolfi and Chainguard APKs
  • DEPRECATED: USE "github>elastic/renovate-config//presets/base" instead
  • Capture APK packages provided by Chainguard (https://ela.st/wolfi)
  • Capture packages annotated with # renovate: datasource=... depName=... headers; via https://renovate-docs.elastic.dev/modules/manager/dockerfile/
  • Renovate configuration to manage containers in docker.elastic.co/ci-agent-images/*. This is included by default and doesn't need to be explicitly pulled in
  • Group Chainguard packages, including Wolfi and Chainguard APKs
  • Baseline configuration for our internal setup
  • 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.
  • Pin Docker digests.
  • Pin github-action digests.
  • Enable Renovate configuration migration PRs when needed.
  • Pin dependency versions for devDependencies.
  • Shared Renovate configuration for an out-of-the-box set of defaults for Renovate at Elastic

🔡 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 1 Pull Request:

fix(deps): update dependency @​elastic/elasticsearch to v9
  • Schedule: ["at any time"]
  • Branch name: renovate/elastic-elasticsearch-9.x
  • Merge into: main
  • Upgrade @elastic/elasticsearch to ^9.0.0

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

@elastic-renovate-prod elastic-renovate-prod bot requested a review from a team as a code owner March 23, 2026 13:56
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