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/addToProject.yml (github-actions)
• .github/workflows/labeler.yml (github-actions)
• .github/workflows/tav.yml (github-actions)
• .github/workflows/test.yml (github-actions)
• .github/workflows/update-specs.yml (github-actions)
• package.json (npm)
• packages/ecs-helpers/package.json (npm)
• packages/ecs-morgan-format/package.json (npm)
• packages/ecs-pino-format/package.json (npm)
• packages/ecs-winston-format/package.json (npm)
• utils/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 14 Pull Requests:

chore(deps): pin dependencies

• Schedule: ["at any time"]
• Branch name: renovate/pin-dependencies
• Merge into: main
• Pin @hapi/hapi to 20.3.0
• Pin @​types/pino to 6.3.12
• Upgrade actions/checkout to 692973e3d937129bcbf40652eb9f2f61becf3332
• Upgrade actions/github-script to 60a0d83039c74a4aee543508d2ffcb1c3799cdea
• Upgrade actions/setup-node to 1e60f620b9541d16bece96c5465dc8ee9832be0b
• Pin ajv to 7.2.4
• Pin ajv-formats to 1.6.1
• Pin autocannon to 7.15.0
• Pin elastic-apm-node to 3.51.0
• Upgrade elastic/apm-pipeline-library to 0abb7c92aa7ed263e7d896db50a1ad3389c3fca1
• Upgrade elastic/oblt-actions to 095f952145365daec1798d9914dd97f1a8930517
• Pin express to 4.19.2
• Pin glob to 7.2.3
• Pin js-yaml to 3.14.1
• Pin morgan to 1.10.0
• Pin pino to 6.14.0
• Pin pino-http to 5.8.0
• Pin semver to 7.6.3
• Pin split2 to 3.2.2
• Pin standard to 16.0.4
• Pin tap to 15.2.3
• Pin test-all-versions to 5.0.1
• Pin ts-node to 10.9.2
• Pin winston to 3.14.1

chore(deps): update dependency @​hapi/hapi to v21

• Schedule: ["at any time"]
• Branch name: renovate/major-hapijs-monorepo
• Merge into: main
• Upgrade @hapi/hapi to ^21.0.0

chore(deps): update dependency @​types/pino to v7

• Schedule: ["at any time"]
• Branch name: renovate/pino-7.x
• Merge into: main
• Upgrade @​types/pino to ^7.0.0

chore(deps): update dependency ajv to v8

• Schedule: ["at any time"]
• Branch name: renovate/ajv-8.x
• Merge into: main
• Upgrade ajv to ^8.0.0

chore(deps): update dependency ajv-formats to v3

• Schedule: ["at any time"]
• Branch name: renovate/ajv-formats-3.x
• Merge into: main
• Upgrade ajv-formats to ^3.0.0

chore(deps): update dependency elastic-apm-node to v4

• Schedule: ["at any time"]
• Branch name: renovate/elastic-apm-node-4.x
• Merge into: main
• Upgrade elastic-apm-node to ^4.0.0

chore(deps): update dependency glob to v11

• Schedule: ["at any time"]
• Branch name: renovate/glob-11.x
• Merge into: main
• Upgrade glob to ^11.0.0

chore(deps): update dependency js-yaml to v4

• Schedule: ["at any time"]
• Branch name: renovate/js-yaml-4.x
• Merge into: main
• Upgrade js-yaml to ^4.0.0

chore(deps): update dependency pino to v9

• Schedule: ["at any time"]
• Branch name: renovate/pino-9.x
• Merge into: main
• Upgrade pino to ^9.0.0

chore(deps): update dependency pino-http to v10

• Schedule: ["at any time"]
• Branch name: renovate/pino-http-10.x
• Merge into: main
• Upgrade pino-http to ^10.0.0

chore(deps): update dependency split2 to v4

• Schedule: ["at any time"]
• Branch name: renovate/split2-4.x
• Merge into: main
• Upgrade split2 to ^4.0.0

chore(deps): update dependency standard to v17

• Schedule: ["at any time"]
• Branch name: renovate/standard-17.x
• Merge into: main
• Upgrade standard to ^17.0.0
• Upgrade standard to 17.x

chore(deps): update dependency tap to v21

• Schedule: ["at any time"]
• Branch name: renovate/tap-21.x
• Merge into: main
• Upgrade tap to ^21.0.0

chore(deps): update dependency test-all-versions to v6

• Schedule: ["at any time"]
• Branch name: renovate/test-all-versions-6.x
• Merge into: main
• Upgrade test-all-versions to ^6.0.0

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

[v1v]

As far as i know we use dependabot in this repository, I'll close this now

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