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

• .github/workflows/ci-plugin.yml (github-actions)
• package.json (npm)

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

chore(deps): pin dependencies

• Schedule: ["at any time"]
• Branch name: renovate/pin-dependencies
• Merge into: master
• Pin @hapi/code to 8.0.7
• Pin @hapi/hapi to 20.3.0
• Pin @hapi/lab to 24.7.1
• Pin @hapi/wreck to 17.2.0
• Upgrade actions/checkout to ee0669bd1cc54295c223e0bb666b733df41de1c5
• Upgrade actions/setup-node to f1f314fca9dfce2769ece7d933488f076716723e

chore(deps): update actions/checkout action to v4

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

chore(deps): update actions/setup-node action to v4

• Schedule: ["at any time"]
• Branch name: renovate/actions-setup-node-4.x
• Merge into: master
• Upgrade actions/setup-node to 0a44ba7841725637a19e28fa30b79a866c81b0a6

chore(deps): update hapijs monorepo (major)

• Schedule: ["at any time"]
• Branch name: renovate/major-hapijs-monorepo
• Merge into: master
• Upgrade @hapi/code to 9.x
• Upgrade @hapi/hapi to 21.x
• Upgrade @hapi/hoek to 11.x
• Upgrade @hapi/lab to 25.x
• Upgrade @hapi/validate to 2.x
• Upgrade @hapi/wreck to 18.x

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

[nuugen]

Closing stale Renovate Onboarding PR (unmerged since creation >30 days ago).

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