Configure Renovate

[elastic-renovate-prod]

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

• .buildkite/rest-tests.yaml (buildkite)
• .github/Dockerfile (dockerfile)
• .github/workflows/backport.yml (github-actions)
• .github/workflows/tests.yml (github-actions)
• pyproject.toml (pep621)
• .buildkite/rest-tests.yaml (regex)
• .github/Dockerfile (regex)
• .buildkite/rest-tests.yaml (regex)
• .github/Dockerfile (regex)

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)
• Chainguard Renovate configuration (https://ela.st/wolfi)
• 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.
• Pin Docker digests.
• Pin github-action digests.
• Pin dependency versions for devDependencies.
• Preset with best practices from the Renovate maintainers. Recommended for advanced users, who want to follow our best practices.
• 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 6 Pull Requests:

Pin dependencies

• Schedule: ["at any time"]
• Branch name: renovate/pin-dependencies
• Merge into: main
• Upgrade actions/checkout to f43a0e5ff2bd294095638e18286ca9a3d1956744
• Upgrade actions/checkout to eef61447b9ff4aafe5dcd4e0bbf5d482be7e7871
• Upgrade actions/setup-python to 65d7f2d534ac1bc67fcd62888c5f4f3d2cb2b236
• Upgrade python to sha256:45803c375b95ea33f482e53a461eca8f247617667d703660a06ccf5eb3d05326
• Upgrade python to sha256:05855f5bf06f5a004b0c1a8aaac73a9d9ea54390fc289d3e80ef52c4f90d5585

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 to v2.5.0

Update python Docker tag to v3.13

• Schedule: ["at any time"]
• Branch name: renovate/python-3.x
• Merge into: main
• Upgrade python to sha256:45803c375b95ea33f482e53a461eca8f247617667d703660a06ccf5eb3d05326

Update actions/checkout action to v4

• Schedule: ["at any time"]
• Branch name: renovate/actions-checkout-4.x
• Merge into: main
• Upgrade actions/checkout to eef61447b9ff4aafe5dcd4e0bbf5d482be7e7871

Update actions/setup-python action to v5

• Schedule: ["at any time"]
• Branch name: renovate/actions-setup-python-5.x
• Merge into: main
• Upgrade actions/setup-python to f677139bbe7f9c59b41e40162b753c062f5d49a3

Update dependency docs/sphinx to v8

• Schedule: ["at any time"]
• Branch name: renovate/docs-sphinx-8.x
• Merge into: main
• Upgrade docs/sphinx to ==8.0.2

🚸 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]

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.