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

• Gemfile (bundler)
• .circleci/config.yml (circleci)

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

Pin dependencies

• Schedule: ["at any time"]
• Branch name: renovate/pin-dependencies
• Merge into: master
• Upgrade jruby to sha256:0757973dd8f2439357d1a1b488b483249c6bbe4045777be15c196b742d54386b
• Upgrade jruby to sha256:6469bd2376cc4b35b5a3b66afbe49c54a61dd60690409b998ff196f3a8e63932
• Upgrade ruby to sha256:dcb8a8a6ee981f949da505cb9f4f15cde696e7bcb088955bc1f92f23a4cd7a72
• Upgrade ruby to sha256:2347de892e419c7160fc21dec721d5952736909f8c3fbb7f84cb4a07aaf9ce7d
• Upgrade ruby to sha256:a79c8ddb7f3d3748427e2d3a45dcae6d42f1d80d9ae3b98959b3a27b220bf434
• Upgrade ruby to sha256:ecc3e4f5da13d881a415c9692bb52d2b85b090f38f4ad99ae94f932b3598444b
• Upgrade ruby to sha256:c15e108473724fd2fde6045657f905b411eea638be1ca97713a462e90db78da7

Update jruby Docker tag to v9.4.14

• Schedule: ["at any time"]
• Branch name: renovate/jruby-9.x
• Merge into: master
• Upgrade jruby to sha256:9b5c270c35a22af73a7e8f33ee522f10413d062f4c19aba066e4c41726b7c0e1

Update ruby Docker tag to v2.7

• Schedule: ["at any time"]
• Branch name: renovate/ruby-2.x
• Merge into: master
• Upgrade ruby to sha256:2347de892e419c7160fc21dec721d5952736909f8c3fbb7f84cb4a07aaf9ce7d

Update jruby Docker tag to v10

• Schedule: ["at any time"]
• Branch name: renovate/jruby-10.x
• Merge into: master
• Upgrade jruby to sha256:d36fc7845f08f46856329ee1231d580994184d1afcdcf728a1917f03f4dc7196

Update ruby Docker tag to v3.4

• Schedule: ["at any time"]
• Branch name: renovate/ruby-3.x
• Merge into: master
• Upgrade ruby to sha256:4bef3ee023c0525189f1907ac256bc4511cc9ef4d5dc088c20b5c5a478638e28

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