chore: Configure Renovate

[renovate]

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/annotate-test-reports.yml (github-actions)
• .github/workflows/cla.yml (github-actions)
• .github/workflows/codeql.yml (github-actions)
• .github/workflows/coverage.yml (github-actions)
• .github/workflows/dependency-review.yml (github-actions)
• .github/workflows/docs.yml (github-actions)
• .github/workflows/issues-to-projects.yml (github-actions)
• .github/workflows/lock-threads.yml (github-actions)
• .github/workflows/pr-coverage.yml (github-actions)
• .github/workflows/publish.yml (github-actions)
• .github/workflows/stale.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
• 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.
• Apply crowd-sourced package replacement rules.
• Apply crowd-sourced workarounds for known problems with packages.
• Do not separate patch and minor upgrades into separate PRs for the same dependency.
• Raise PR when vulnerability alerts are detected with label vulnerability.
• Limit to maximum 10 open PRs at any time.
• Rate limit PR creation to a maximum of four per hour.
• Wait for branch tests to pass or fail before creating the PR.
• Preserve (but continue to upgrade) any existing SemVer ranges.
• Rebase existing PRs any time the base branch has been updated.
• Use semantic prefixes for commit messages and PR titles.
• Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
• Apply label dependencies to PRs.
• Evaluate schedules according to timezone Europe/London.
• Enable Docker major updates.
• Pin Docker digests.
• Group PostCSS packages together.
• Group various lint packages together.
• Group known monorepo packages together.
• Wait until the npm package is three days old before raising the update, this prevents npm unpublishing a package you already upgraded to.
• Update _VERSION variables in Dockerfiles.
• Apply crowd-sourced package replacement rules.

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

chore(deps): update actions/add-to-project action to v0.6.1

• Schedule: ["at any time"]
• Branch name: renovate/actions-add-to-project-0.x
• Merge into: canary
• Upgrade actions/add-to-project to v0.6.1

chore(deps): update contributor-assistant/github-action action to v2.6.1

• Schedule: ["at any time"]
• Branch name: renovate/contributor-assistant-github-action-2.x
• Merge into: canary
• Upgrade contributor-assistant/github-action to v2.6.1

chore(deps): update dependency typedoc to ^0.27.0

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

chore(deps): update actions/add-to-project action to v1

• Schedule: ["at any time"]
• Branch name: renovate/actions-add-to-project-1.x
• Merge into: canary
• Upgrade actions/add-to-project to v1.0.2

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

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

chore(deps): update actions/configure-pages action to v5

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

chore(deps): update actions/dependency-review-action action to v4

• Schedule: ["at any time"]
• Branch name: renovate/actions-dependency-review-action-4.x
• Merge into: canary
• Upgrade actions/dependency-review-action to v4

chore(deps): update actions/deploy-pages action to v4

• Schedule: ["at any time"]
• Branch name: renovate/actions-deploy-pages-4.x
• Merge into: canary
• Upgrade actions/deploy-pages to v4

chore(deps): update actions/stale action to v9

• Schedule: ["at any time"]
• Branch name: renovate/actions-stale-9.x
• Merge into: canary
• Upgrade actions/stale to v9

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

• Schedule: ["at any time"]
• Branch name: renovate/actions-upload-pages-artifact-3.x
• Merge into: canary
• Upgrade actions/upload-pages-artifact to v3

chore(deps): update dependency @​cucumber/cucumber to v11

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

chore(deps): update dependency @sebbo2002/semantic-release-jsr to v2

• Schedule: ["at any time"]
• Branch name: renovate/sebbo2002-semantic-release-jsr-2.x
• Merge into: canary
• Upgrade @sebbo2002/semantic-release-jsr to ^2.0.0

chore(deps): update dependency @semantic-release/github to v11

• Schedule: ["at any time"]
• Branch name: renovate/major-semantic-release-monorepo
• Merge into: canary
• Upgrade @semantic-release/github to ^11.0.0

chore(deps): update dependency c8 to v10

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

chore(deps): update dependency chai to v5

• Schedule: ["at any time"]
• Branch name: renovate/chai-5.x
• Merge into: canary
• Upgrade chai to ^5.0.0
• Upgrade @types/chai to ^5.0.0

chore(deps): update dependency eslint to v9

• Schedule: ["at any time"]
• Branch name: renovate/major-eslint-monorepo
• Merge into: canary
• Upgrade eslint to ^9.0.0

chore(deps): update dependency mocha to v11

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

chore(deps): update dependency sinon to v19

• Schedule: ["at any time"]
• Branch name: renovate/sinon-19.x
• Merge into: canary
• Upgrade sinon to ^19.0.0

chore(deps): update dessant/lock-threads action to v5

• Schedule: ["at any time"]
• Branch name: renovate/dessant-lock-threads-5.x
• Merge into: canary
• Upgrade dessant/lock-threads to v5

chore(deps): update github/codeql-action action to v3

• Schedule: ["at any time"]
• Branch name: renovate/github-codeql-action-3.x
• Merge into: canary
• Upgrade github/codeql-action to v3

chore(deps): update oven-sh/setup-bun action to v2

• Schedule: ["at any time"]
• Branch name: renovate/oven-sh-setup-bun-2.x
• Merge into: canary
• Upgrade oven-sh/setup-bun to v2

chore(deps): update paambaati/codeclimate-action action to v9

• Schedule: ["at any time"]
• Branch name: renovate/paambaati-codeclimate-action-9.x
• Merge into: canary
• Upgrade paambaati/codeclimate-action to v9.0.0

chore(deps): update typescript-eslint monorepo to v8 (major)

• Schedule: ["at any time"]
• Branch name: renovate/major-typescript-eslint-monorepo
• Merge into: canary
• Upgrade @typescript-eslint/eslint-plugin to ^8.0.0
• Upgrade @typescript-eslint/parser to ^8.0.0

chore(deps): update zgosalvez/github-actions-report-lcov action to v4

• Schedule: ["at any time"]
• Branch name: renovate/zgosalvez-github-actions-report-lcov-4.x
• Merge into: canary
• Upgrade zgosalvez/github-actions-report-lcov to v4

🚸 Branch creation will be limited to maximum 4 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.

[github-actions]

LCOV of commit f92da4f during Comment PR Coverage #39

Summary coverage rate:
  lines......: 97.6% (880 of 902 lines)
  functions..: 100.0% (34 of 34 functions)
  branches...: 94.3% (164 of 174 branches)

Files changed coverage rate: n/a