Skip to content

Configure Renovate#7149

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

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

Conversation

@elastic-renovate-prod
Copy link

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

  • .github/workflows/co-docs-builder.yml (github-actions)
  • .github/workflows/delete-serverless-dir-in-backports.yml (github-actions)
  • .github/workflows/docs-build.yml (github-actions)
  • .github/workflows/docs-cleanup.yml (github-actions)
  • .github/workflows/docs-preview.yml (github-actions)
  • requirements-rules.txt (pip_requirements)

Configuration Summary

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

  • Start dependency updates only once this onboarding PR is merged
  • Chainguard Renovate configuration (https://ela.st/wolfi)
  • 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
  • Chainguard Renovate configuration (https://ela.st/wolfi)
  • 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
  • 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 4 Pull Requests:

Pin actions/checkout action to 34e1148
  • Schedule: ["at any time"]
  • Branch name: renovate/pin-dependencies
  • Merge into: main
  • Upgrade actions/checkout to 34e114876b0b11c390a56381ad16ebd13914f8d5
Update actions/checkout action to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-6.x
  • Merge into: main
  • Upgrade actions/checkout to de0fac2e4500dabe0009e67214ff5f5447ce83dd
Update dependency PyYAML to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/pyyaml-6.x
  • Merge into: main
  • Upgrade PyYAML to ==6.0.3
Update dependency click to v8
  • Schedule: ["at any time"]
  • Branch name: renovate/click-8.x
  • Merge into: main
  • Upgrade click to ==8.3.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.

@elastic-renovate-prod elastic-renovate-prod bot requested a review from a team as a code owner February 28, 2026 01:43
@github-actions
Copy link

A documentation preview will be available soon.

Request a new doc build by commenting
  • Rebuild this PR: run docs-build
  • Rebuild this PR and all Elastic docs: run docs-build rebuild

run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.

If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.

@mergify
Copy link
Contributor

mergify bot commented Feb 28, 2026

This pull request does not have a backport label. Could you fix it @elastic-renovate-prod[bot]? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • v7.x is the label to automatically backport to the 7.x branch.
  • v7./d./d is the label to automatically backport to the 7./d branch. /d is the digit

NOTE: backport-skip has been added to this pull request.

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