chore: update configuration files and dependencies to latest versions

[Adammatthiesen]

Description

• Closes #
• What does this PR change? Give us a brief description.

Summary by CodeRabbit

• Chores
  • Raised required Node.js version to 22.19.0 for local development and CI.
  • Centralized Renovate configuration by switching to a shared extends entry.
  • Removed an unused tooling plugin and pointed a schema reference to a local copy for reliability.
  • Relaxed multiple devDependencies to caret ranges to allow minor/patch updates.
  • Added a changeset and relaxed a package peer dependency for @astrojs/db (>=0.17.1).

[changeset-bot]

🦋 Changeset detected

Latest commit: b5408ea

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@studiocms/web-vitals	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[coderabbitai]

📝 Walkthrough

Walkthrough

Replaces local Renovate config with a single shared extends entry, updates Node from 20.14.0 → 22.19.0 across project files, removes Biome plugin declaration and points biome.json schema to a local file, and loosens several devDependency versions to caret ranges.

Changes

Cohort / File(s)	Summary
Renovate config centralization .github/renovate.json	Replaced extensive local Renovate configuration with "extends": ["github>withstudiocms/renovate-config"].
Node runtime/version bumps .node-version, .prototools, package.json	Updated Node version from 20.14.0 to 22.19.0 in .node-version, .prototools, and package.json engines.
Biome tooling adjustments .prototools, biome.json	Removed biome top-level setting and [plugins] block from .prototools; changed biome.json $schema to local ./node_modules/@biomejs/biome/configuration_schema.json.
Dependency range loosening package.json	Converted multiple devDependencies from fixed versions to caret ranges (e.g., @biomejs/biome, @changesets/*, @types/node, @withstudiocms/buildkit, knip, pkg-pr-new).
Changeset / package metadata .changeset/slow-deer-change.md, packages/web-vitals/package.json	Added a changeset for @studiocms/web-vitals (patch) and relaxed peerDependencies["@astrojs/db"] to >=0.17.1 in packages/web-vitals/package.json.

Sequence Diagram(s)

No control-flow or runtime feature changes were introduced that require a sequence diagram.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related issues

• Dependency Dashboard automations#9 — Both modify .github/renovate.json; this PR centralizes Renovate config which relates to the Automations Renovate setup.
• Dependency Dashboard studiocms#30 — Renovate config consolidation here affects Renovate behavior referenced by that issue.
• withstudiocms/cli-utilities#1 — This PR updates devDependency declarations and Renovate config, which overlap with concerns in the CLI utilities Renovate/dependency issue.
• Dependency Dashboard #5 — Peer-dependency and changeset edits in this PR align with dependency/dashboard concerns raised in that issue.

Possibly related PRs

• 👷 [ci]: Ready for Release #18 — Also modifies packages/web-vitals metadata and release/dependency artifacts; closely related to the changeset and peerDependency edits.
• 👷 [ci]: Ready for Release #22 — Involves publishing/patching web-vitals; related to the changeset and dependency constraint changes here.
• Fix peer dep #19 — Touches the same @astrojs/db peerDependency field that this PR updates (conflicting/overlapping edits).

Suggested reviewers

• dreyfus92
• louisescher
• jdtjenkins

Poem

In a burrow of JSON I found a small nest,
I nudged Renovate to use one shared crest.
Node hopped to twenty-two, tidy and spry,
Biome's plugin waved its last goodbye.
Caret-carrots sprout—dependencies sigh, thump! 🥕🐇

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title concisely and accurately summarizes the primary work in the changeset — updating configuration files and dependency/version constraints across the repository — and is specific enough for a reviewer to understand the main intent without listing files or extraneous detail. It is brief, clear, and directly related to the changes shown in the diff.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch adam/cleanup

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8b5e977 and b5408ea.

📒 Files selected for processing (2)

• .changeset/slow-deer-change.md (1 hunks)
• packages/web-vitals/package.json (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• .changeset/slow-deer-change.md

🔇 Additional comments (1)

packages/web-vitals/package.json (1)

57-58: Bound @astrojs/db peer range to ^0.17.1

Change the peerDependency to "^0.17.1" to avoid accepting breaking 0.x minor bumps — repo scan found only this peer entry (packages/web-vitals/package.json) and no other dependency/dev/dev-catalog entries that would conflict.

-    "@astrojs/db": ">=0.17.1"
+    "@astrojs/db": "^0.17.1"

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

🧹 Nitpick comments (2)

package.json (2)

6-6: Consider a range for engines to avoid pinning to a single patch.
Exact pin blocks Node 22 patch updates on dev/CI machines. Suggested:

-    "node": "22.19.0"
+    "node": ">=22.19.0 <23"

---

29-29: Avoid caret on prerelease (beta) dependency to reduce CI drift.
Caret on 0.x prereleases can pull newer betas unexpectedly. Prefer exact or tilde.

-    "@withstudiocms/buildkit": "^0.1.0-beta.4",
+    "@withstudiocms/buildkit": "~0.1.0-beta.4",

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 10adf2b and 8b5e977.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (5)

• .github/renovate.json (1 hunks)
• .node-version (1 hunks)
• .prototools (1 hunks)
• biome.json (1 hunks)
• package.json (2 hunks)

🔇 Additional comments (3)

biome.json (1)

2-2: LGTM: switch to local Biome schema path.
This improves offline validation. Note: editors may show a transient “schema not found” until node_modules is installed.

.prototools (1)

1-2: Confirm pnpm 10.17.0 compatibility with Node 22 and intentional Biome plugin removal.
Per PR summary, the Biome plugin/section was removed. Ensure any proto-based flows don’t rely on it and that CI uses the devDependency CLI.

.node-version (1)

1-1: Node 22.19.0 confirmed and consistent repo-wide.
.node-version, package.json (engines.node) and .prototools all set to 22.19.0; Node v22.19.0 exists upstream.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/withstudiocms/web-vitals/@studiocms/web-vitals@40

commit: b5408ea