chore: reconfigure renovate

[cheefbird]

Updating renovate config and pnpm workspace w security rec's.

[renovate]

Reconfigure PR Results

This is a reconfigure PR comment to help you understand and re-configure your renovate bot settings. If this Reconfigure PR were to be merged, we'd expect to see the following outcome:

---

Detected Package Files

• .github/workflows/ci.yml (github-actions)
• .github/workflows/publish.yml (github-actions)
• .github/workflows/release.yml (github-actions)
• package.json (npm)
• pnpm-workspace.yaml (npm)
• .nvmrc (nvm)

Configuration Summary

Based on the default config's presets, Renovate will:

• 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.
• Ensure that every dependency pinned by digest and sourced from Forgejo contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from GitLab.com contains a link to the commit-to-commit diff
• Correctly link to the source code for golang.org/x packages
• Link to pkg.go.dev/... for golang.org/x packages' title
• Provide a link to octochangelog's improved breakdown for Renovate's changelogs
• Pin Docker digests.
• Pin github-action digests.
• Enable Renovate configuration migration PRs when needed.
• Pin dependency versions for development dependencies.
• Recommended configuration for abandoned packages, treating packages without a release for 1 year as abandoned, while taking into account community-sourced overrides.
• Wait until the npm package is three days old before raising the update. This a) introduces a short delay to allow for malware researchers and scanners to (possibly) detect any malicious behaviour in packages, and b) prevents the maintainer and/or NPM from unpublishing a package you already upgraded to, breaking builds.
• Run lock file maintenance (updates) early Monday mornings.
• Convert pinned GitHub Action digests to SemVer.
• Show all Merge Confidence badges for pull requests.
• Apply crowd-sourced workarounds for known problems with packages.
• Run Renovate on following schedule: after 4pm,before 8am

---

What to Expect

With your current configuration, Renovate will create 3 Pull Requests:

chore(deps): update test infrastructure

• Schedule: ["after 4pm","before 8am"]
• Branch name: renovate/test-infrastructure
• Merge into: main
• Upgrade happy-dom to 20.10.4
• Upgrade vitest to 4.1.9

chore(deps): update pnpm to v11.7.0

• Schedule: ["after 4pm","before 8am"]
• Branch name: renovate/pnpm-11.x
• Merge into: main
• Upgrade pnpm to 11.7.0

chore(deps): lock file maintenance

• Schedule: ["* 0-3 * * 1"]
• Branch name: renovate/lock-file-maintenance
• Merge into: main
• Regenerate lock files to use latest dependency versions