[mvantellingen]

pnpm 12

• packageManager: pnpm@12.12.0 added (pnpm 12 applies minimumReleaseAge to its own version; 12.12.0 is the newest 12.x older than 14 days)
• new pnpm-workspace.yaml: minimumReleaseAge: 20160 (14 days), and allowBuilds: esbuild: false (pnpm 11+ blocks build scripts by default; esbuild's postinstall isn't needed)
• pnpm-lock.yaml: lockfile v6 → v9 (converted with pnpm 9 first, because pnpm 12 ignores a v6 lockfile and re-resolves). The set of resolved name@version entries is identical before/after; the diff is format only plus the packageManagerDependencies document for pnpm itself
• pnpm-lock.yaml added to .prettierignore (the v6 lockfile used to be prettier-formatted; pnpm 12 rewrites it in its own style)
• CI: pnpm/action-setup v3 → v6.1.0 without the hard-coded version: 8 (reads packageManager); release job runs on Node 24 (was 18, unsupported by pnpm 12) and no longer caches the pnpm store
• Not switched to labd/gh-actions-typescript/pnpm-install: its pnpm audit --audit-level=critical step fails on the current vitest 1.3.0 (GHSA-9crc-q9x8-hgqq etc.); upgrading vitest is out of scope here

Biome

• Replaced prettier (+ prettier-plugin-organize-imports, prettier-plugin-packagejson) and eslint (eslint, @typescript-eslint/eslint-plugin, eslint-plugin-unused-imports) with @biomejs/biome 2.5.15, configured via biome.jsonc (modeled on commercetools-node-mock: tabs, double quotes, recommended rules, noUnusedImports, noConsole allowing warn/error/info).
• Import sorting is now done by biome's organizeImports assist. There is no biome equivalent of prettier-plugin-packagejson, so package.json key sorting is dropped.
• Scripts: lint = biome check, format = biome check --fix, new check = biome check && tsc --noEmit. generate-docs no longer runs prettier on README.md (biome does not format markdown).
• CI runs pnpm biome ci.
• Formatting changes are in a separate style: format with biome commit.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 7d5057e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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