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/build-and-deploy.yml (github-actions)
• .github/workflows/checks.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 8 Pull Requests:

chore(deps): update babel monorepo to v7.28.5

• Schedule: ["at any time"]
• Branch name: renovate/babel-monorepo
• Merge into: master
• Upgrade @babel/core to 7.28.5
• Upgrade @babel/preset-env to 7.28.5
• Upgrade @babel/preset-typescript to 7.28.5

chore(deps): update dependency @​rollup/plugin-commonjs to v28.0.9

• Schedule: ["at any time"]
• Branch name: renovate/rollup-plugin-commonjs-28.x-lockfile
• Merge into: master
• Upgrade @rollup/plugin-commonjs to 28.0.9

chore(deps): update dependency lint-staged to v16.2.6

• Schedule: ["at any time"]
• Branch name: renovate/lint-staged-16.x-lockfile
• Merge into: master
• Upgrade lint-staged to 16.2.6

chore(deps): update dependency typescript-eslint to v8.46.2

• Schedule: ["at any time"]
• Branch name: renovate/typescript-eslint-monorepo
• Merge into: master
• Upgrade typescript-eslint to 8.46.2

chore(deps): update dependency @​types/node to v24.9.1

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

chore(deps): update pnpm to v9.15.9

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

chore(deps): update dependency @​types/jquery to v3

• Schedule: ["at any time"]
• Branch name: renovate/jquery-3.x
• Merge into: master
• Upgrade @types/jquery to ^3.0.0

chore(deps): update pnpm to v10

• Schedule: ["at any time"]
• Branch name: renovate/pnpm-10.x
• Merge into: master
• Upgrade pnpm to 10.19.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 was generated by Mend Renovate. View the repository job log.

[arsinclair]

We probably shouldn't allow it to upgrade to major versions. For example upgrading @​types/jquery to v3 is incorrect, since the scripts are using v2 and this upgrade will lead to type issues in the code.

Major upgrades almost as a rule should involve human intervention, since it's very important to read the changelogs and adjust the systems for any breaking changes or deprecations.

[murdos]

A major upgrade will never be auto merged.
For jQuery, we can configure renovate to ignore any upgrade.

[arsinclair]

Alright, great! Thank you for the change.