chore: Configure Renovate

[renovate]

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 Renovate will begin keeping your dependencies up-to-date only once you merge or close this Pull Request.

---

Detected Package Files

• Dockerfile (dockerfile)
• .github/workflows/on-push-tag.yaml (github-actions)
• .github/workflows/release-init.yml (github-actions)
• .github/workflows/release-pr-merged.yml (github-actions)
• .github/workflows/release-pr.yml (github-actions)
• .github/workflows/test.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
• Hopefully safe environment variables to allow users to configure.
• Show all Merge Confidence badges for pull requests.
• 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.
• Show only the Age and Confidence Merge Confidence badges for pull requests.
• Apply crowd-sourced package replacement rules.
• Apply crowd-sourced workarounds for known problems with packages.

🔡 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 10 Pull Requests:

chore(deps): update dependency @​actions/core to v1.11.1

• Schedule: ["at any time"]
• Branch name: renovate/actions-core-1.x-lockfile
• Merge into: main
• Upgrade @actions/core to 1.11.1

chore(deps): update dependency @​types/node to v20.19.24

• Schedule: ["at any time"]
• Branch name: renovate/node-20.x-lockfile
• Merge into: main
• Upgrade @types/node to 20.19.24

chore(deps): update dependency esbuild to ^0.27.0

• Schedule: ["at any time"]
• Branch name: renovate/esbuild-0.x
• Merge into: main
• Upgrade esbuild to ^0.27.0

chore(deps): update dependency typescript to v5.9.3

• Schedule: ["at any time"]
• Branch name: renovate/typescript-5.x-lockfile
• Merge into: main
• Upgrade typescript to 5.9.3

chore(deps): update yarn to v4.11.0

• Schedule: ["at any time"]
• Branch name: renovate/yarn-monorepo
• Merge into: main
• Upgrade yarn to 4.11.0

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

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

chore(deps): update actions/upload-artifact action to v5

• Schedule: ["at any time"]
• Branch name: renovate/major-github-artifact-actions
• Merge into: main
• Upgrade actions/upload-artifact to v5

chore(deps): update dependency @​actions/io to v2

• Schedule: ["at any time"]
• Branch name: renovate/actions-io-2.x
• Merge into: main
• Upgrade @actions/io to ^2.0.0

chore(deps): update node.js to v24

• Schedule: ["at any time"]
• Branch name: renovate/node-24.x
• Merge into: main
• Upgrade node to 24-alpine
• Upgrade @types/node to ^24.0.0

chore(deps): update peter-evans/create-pull-request action to v7

• Schedule: ["at any time"]
• Branch name: renovate/peter-evans-create-pull-request-7.x
• Merge into: main
• Upgrade peter-evans/create-pull-request to v7

🚸 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 was generated by Mend Renovate. View the repository job log.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud