@lenne.tech/nest-server 11.29.0 → 11.29.1

package/.claude/rules/package-management.md

@@ -4,7 +4,7 @@ This document defines the rules for managing dependencies in package.json.
 
 ## Package Manager: pnpm
 
-This project uses **pnpm** for development. The `packageManager` field in `package.json` ensures the correct version is used (via Corepack).
+This project uses **pnpm** for development. The `packageManager` field in `package.json` pins the exact version and is the single source of truth — pnpm itself follows it (`managePackageManagerVersions`, on by default since pnpm 10), so no Corepack is involved. See [The pnpm pin contract](#the-pnpm-pin-contract-packagemanager-as-single-source-of-truth).
 
 ```bash
 # Install dependencies
@@ -99,7 +99,7 @@ The `pnpm-lock.yaml` file must always be committed. It provides additional repro
 
 ## Package Manager: pnpm 11
 
-This repo is pinned to **pnpm 11** via the `packageManager` field (corepack/`pnpm/action-setup` follow it, so CI and Docker use it automatically — no version is hardcoded anywhere else).
+This repo is pinned to **pnpm 11** via the `packageManager` field — see [The pnpm pin contract](#the-pnpm-pin-contract-packagemanager-as-single-source-of-truth) for how CI and Docker consume it without corepack.
 
 pnpm 11 **no longer reads the `pnpm` field in `package.json`**, and `.npmrc` is auth/registry only. All pnpm-specific settings live in **`pnpm-workspace.yaml`**:
 
@@ -109,6 +109,61 @@ pnpm 11 **no longer reads the `pnpm` field in `package.json`**, and `.npmrc` is
 
 `pnpm audit`: pnpm 10.x is broken (npm retired the legacy audit endpoint → HTTP 410); pnpm 11 uses the working bulk-advisory endpoint. `scripts/check.mjs` degrades the retired-endpoint failure to a non-blocking warning as a safety net, so `check` stays green + honest even if a future endpoint change lands.
 
+## The pnpm pin contract: `packageManager` as single source of truth
+
+**Rule: the pnpm version is pinned in exactly one place — `package.json#packageManager`. Nothing may hardcode it, and nothing may rely on corepack.**
+
+```jsonc
+{
+  "packageManager": "pnpm@11.13.1+sha512.b2fc7683…",  // THE pin: exact, with integrity hash
+  "engines": { "node": ">= 22", "pnpm": "^11.0.0" }   // soft major gate — NOT a pin
+}
+```
+
+**Corepack is not part of this contract.** It used to be the thing that read `packageManager`, but **Node >= 25 no longer ships it** — a build stage running `corepack enable` on such an image dies with `corepack: not found`. Nothing here needs it: pnpm follows the field itself (`managePackageManagerVersions`, on by default since pnpm 10), and `pnpm/action-setup` reads it directly.
+
+### How each consumer gets the pinned pnpm
+
+| Consumer | Mechanism |
+|----------|-----------|
+| Local dev | pnpm self-switches to the pinned version (`managePackageManagerVersions`) |
+| GitHub Actions | `pnpm/action-setup@v6` with **no** `version:` input — it reads `packageManager` |
+| Docker / other CI | the derive-line (below), once per pnpm-running stage |
+
+### The derive-line
+
+```dockerfile
+# Provision the exact pnpm declared in package.json (single source of truth).
+# No corepack: Node >= 25 no longer ships it. The +sha512 suffix is stripped;
+# npm enforces registry integrity for the tarball itself.
+RUN npm install -g "$(node -p "require('./package.json').packageManager.split('+')[0]")"
+```
+
+`.split('+')[0]` reduces `pnpm@11.13.1+sha512.…` to the plain spec `npm install -g` accepts. Dropping the hash does not weaken integrity — npm verifies the tarball against the registry's own metadata.
+
+Two ordering rules, both enforced by the contract test:
+
+1. It must run **after** the `COPY` that puts `package.json` in the WORKDIR — it reads that file.
+2. It must be repeated in **every** stage that runs `pnpm`. A global install in `deps` does not survive into `builder`; stages inherit only what is explicitly `COPY --from=`'d.
+
+### Rules
+
+| Rule | Why |
+|------|-----|
+| `packageManager` is exact (`x.y.z+sha512.<hash>`), never a range | Same fixed-version rule as dependencies; corepack rejects ranges outright |
+| `engines.pnpm` tracks the pin's major (`^<major>.0.0`) | A soft gate that warns pnpm 10 users. It is not a pin and cannot tell CI what to install |
+| Never declare `devEngines.packageManager` | npm/npx abort with `EBADDEVENGINES`; corepack rejects ranges inside it |
+| Never pass `version:` to `pnpm/action-setup` | Two sources drift; the action hard-errors on a mismatch |
+| Never `RUN corepack …` | Absent on Node >= 25 |
+| Never `npm install -g pnpm@<literal>` | That is a second pin — derive it instead |
+| Monorepo: pin at the **workspace root** | The derive-line reads `/app/package.json`, which in monorepo mode (`API_DIR=projects/api`) is the root manifest. Missing there → `TypeError: Cannot read properties of undefined (reading 'split')` |
+
+### Enforcement
+
+`tests/unit/pnpm-pin-contract.spec.ts` asserts every rule above structurally (unit suite, no network), so a re-introduced `with: version: 11` or a stray `corepack enable` fails the build rather than drifting silently. A twelfth test proves the chain functionally — derive the spec, `npm install -g` it into a throwaway prefix, assert the binary reports the pinned version. It needs network + ~10 MB and is gated to `CI` / `PIN_PROVISION_TEST=1`.
+
+**When bumping pnpm:** run `pnpm self-update` (writes the field with a fresh hash), align `engines.pnpm` if the major moved, and commit `package.json` + `pnpm-lock.yaml` together. Nothing else needs touching — that is the point.
+
 ## Overrides
 
 Package overrides live in the `overrides:` section of **`pnpm-workspace.yaml`** (they moved out of `package.json`'s `pnpm.overrides` in the pnpm 11 upgrade). They force transitive dependencies to a security-patched version.

package/FRAMEWORK-API.md

@@ -1,6 +1,6 @@
 # @lenne.tech/nest-server — Framework API Reference
 
-> Auto-generated from source code on 2026-07-16 (v11.29.0)
+> Auto-generated from source code on 2026-07-17 (v11.29.1)
 > File: `FRAMEWORK-API.md` — compact, machine-readable API surface for Claude Code
 
 ## CoreModule.forRoot()

package/migration-guides/11.29.0-to-11.29.1.md

@@ -0,0 +1,311 @@
+# Migration Guide: 11.29.0 → 11.29.1
+
+## Overview
+
+| Category | Details |
+|----------|---------|
+| **Breaking Changes** | None |
+| **Bugfixes** | None — no runtime code changed. `src/core/` is byte-identical to 11.29.0. |
+| **New Features** | None |
+| **Maintenance** | **Toolchain only.** `package.json#packageManager` is restored as the *single* place the pnpm version is pinned. `corepack` is gone from the `Dockerfile` (Node >= 25 no longer ships it); every pnpm-running build stage now provisions the pinned pnpm itself. `pnpm/action-setup` reads the pin instead of carrying its own `version` input. A contract test (`tests/unit/pnpm-pin-contract.spec.ts`) guards the whole chain. |
+| **Migration Effort** | **0 minutes for npm-mode and vendor-mode consumers** — nothing in your project changes. **~10 minutes if you adopt the pattern**, which you should do *before* moving any build to Node >= 25. |
+
+This release changes **how the framework repo builds itself**. It ships no API change, no
+configuration change, and no behavioral change. Update with `pnpm add @lenne.tech/nest-server@11.29.1`
+and you are done.
+
+The reason to read further: **the `Dockerfile` is not part of the npm package** (it is not in
+`package.json#files`). Your project's own `Dockerfile` and CI came from the starter template, so you
+do **not** inherit this fix automatically. If they still run `corepack enable`, they will break the
+day you move to Node >= 25 — see [Adopting the pattern](#adopting-the-pattern-in-your-project-recommended).
+
+---
+
+## Quick Migration (npm mode)
+
+No code changes required.
+
+```bash
+# Update the package
+pnpm add @lenne.tech/nest-server@11.29.1
+
+# Verify
+pnpm run build
+pnpm test
+```
+
+---
+
+## Why this release exists: corepack is going away
+
+`corepack` was the mechanism that read `package.json#packageManager` and materialized the right
+package-manager binary. It shipped with Node for years, which is why the framework's `Dockerfile`
+could simply say `corepack enable` and trust that pnpm appeared.
+
+**Node >= 25 no longer ships corepack.** A build stage that runs `corepack enable` on such an image
+fails outright:
+
+```
+/bin/sh: corepack: not found
+```
+
+So the framework needed a way to provision an exact pnpm version that does not depend on corepack
+existing — without giving up the single-source-of-truth pin.
+
+### What 11.29.0 did, and why it is reverted here
+
+11.29.0 removed the `packageManager` field and introduced `engines.pnpm: "^11.0.0"`. That left the
+repo with **no exact pin at all**, so the version had to be restated wherever pnpm was needed — the
+workflows grew a hardcoded `with: version: 11`, and Docker's `corepack enable` (with no
+`packageManager` field to follow) would resolve to whatever it considered current.
+
+Two sources of truth, neither exact. 11.29.1 collapses them back into one:
+
+| | 11.29.0 | 11.29.1 |
+|---|---|---|
+| `package.json#packageManager` | *(removed)* | `pnpm@11.13.1+sha512.…` — **the** pin |
+| `package.json#engines.pnpm` | `^11.0.0` | `^11.0.0` — unchanged, a soft major gate |
+| `.github/workflows/*` | `with: version: 11` | *(no `version` input — reads the pin)* |
+| `Dockerfile` | `corepack enable` | derive-line (below) |
+
+`engines.pnpm` stays, but understand what it is: a **soft major-range guard**, not a pin. It warns a
+pnpm 10 user; it does not tell CI which version to install. Only `packageManager` does that.
+
+---
+
+## What Changed
+
+### 1. `packageManager` is back — exact, with an integrity hash
+
+```jsonc
+// package.json
+{
+  "packageManager": "pnpm@11.13.1+sha512.b2fc7683b8a6525414e7d13e1ba28caaddde96bf66ec540bfaeb7e702b81f3e0be4d1f295edf7f9fe0396740a8dce4509c582ddf79891f4543fea32d37645f25",
+  "engines": {
+    "node": ">= 22",
+    "pnpm": "^11.0.0"
+  }
+}
+```
+
+**This field has no effect on your project.** `packageManager` is only ever read from the *root*
+`package.json` of the project being built — never from a dependency's. You inherit nothing from the
+framework's pin.
+
+Note that pnpm itself honours the field, with no corepack involved: run any `pnpm` command in a
+directory whose `package.json` pins a different pnpm, and pnpm switches to it
+(`managePackageManagerVersions`, on by default since pnpm 10). Corepack was never the only thing
+reading this field — which is exactly why dropping it costs nothing.
+
+### 2. The Dockerfile provisions pnpm without corepack
+
+Every stage that runs `pnpm` now provisions the pinned version itself, from the pin:
+
+```dockerfile
+# Provision the exact pnpm declared in package.json (single source of truth).
+# No corepack: Node >= 25 no longer ships it. The +sha512 suffix is stripped;
+# npm enforces registry integrity for the tarball itself.
+RUN npm install -g "$(node -p "require('./package.json').packageManager.split('+')[0]")"
+```
+
+The `.split('+')[0]` turns `pnpm@11.13.1+sha512.b2fc…` into `pnpm@11.13.1`, because `npm install -g`
+takes a plain spec. The dropped hash is not a loss of integrity: npm verifies the tarball against the
+registry's own integrity metadata on install.
+
+The line appears **once per pnpm-running stage** (`deps` and `builder`) — Docker stages do not inherit
+each other's globally installed binaries, only what is explicitly `COPY --from=`'d.
+
+### 3. `pnpm/action-setup` no longer carries a `version` input
+
+```yaml
+- name: Install pnpm
+  # No version input: the exact version is read from package.json's packageManager field.
+  uses: pnpm/action-setup@v6
+```
+
+The action reads `packageManager` on its own. Specifying **both** is not redundant-but-harmless — the
+action treats a mismatch as a hard error, so the two sources cannot silently drift.
+
+### 4. A contract test guards the chain
+
+`tests/unit/pnpm-pin-contract.spec.ts` (11 assertions, unit suite, no MongoDB) fails the build if
+anyone re-introduces the drift this release removes:
+
+- the pin is exact (`x.y.z` + `sha512` hash — never a range),
+- `engines.pnpm` tracks the pin's major,
+- `devEngines.packageManager` never (re)appears — npm/npx abort with `EBADDEVENGINES` on it,
+- the `Dockerfile` contains no `corepack` in any `RUN`,
+- **every** pnpm-running stage runs the derive-line *before* its first `pnpm` command, and only after
+  a `COPY` has put `package.json` in place,
+- no workflow passes a `version:` to `pnpm/action-setup` or hardcodes `npm install -g pnpm@…`.
+
+A twelfth test proves the chain end-to-end — it derives the spec exactly as the Dockerfile does,
+installs it into a throwaway prefix, and asserts the provisioned binary reports the pinned version.
+It needs network and ~10 MB, so it is gated to `CI` / `PIN_PROVISION_TEST=1` and stays out of your way
+locally.
+
+---
+
+## Breaking Changes
+
+**None.** No public API, config key, decorator, or exported symbol changed.
+
+---
+
+## Adopting the pattern in your project (recommended)
+
+Do this **before** you move any build to Node >= 25 — not after it breaks. If your project was
+generated from a recent `nest-server-starter` / `lt fullstack init`, check whether it is already done.
+
+### Step 1: Pin pnpm in your root `package.json`
+
+```bash
+# Writes packageManager with the integrity hash for the version you actually use
+pnpm self-update
+```
+
+Or set it by hand — the exact form matters (`pnpm@x.y.z+sha512.<hash>`):
+
+```jsonc
+{
+  "packageManager": "pnpm@11.13.1+sha512.b2fc7683…",
+  "engines": { "node": ">= 22", "pnpm": "^11.0.0" }
+}
+```
+
+> **Monorepo:** this belongs in the **workspace root** `package.json`, not only in `projects/api/`.
+> The Dockerfile's derive-line reads `/app/package.json`, which in monorepo mode
+> (`--build-arg API_DIR=projects/api`) is the root manifest. See
+> [Troubleshooting](#docker-build-fails-with-typeerror-cannot-read-properties-of-undefined-reading-split).
+
+### Step 2: Replace corepack in your Dockerfile
+
+**Before:**
+```dockerfile
+RUN apk add --no-cache python3 make g++ && corepack enable
+```
+
+**After:**
+```dockerfile
+RUN apk add --no-cache python3 make g++
+
+# … COPY the manifests first — the derive-line reads package.json …
+
+# Provision the exact pnpm declared in package.json (single source of truth).
+# No corepack: Node >= 25 no longer ships it. The +sha512 suffix is stripped;
+# npm enforces registry integrity for the tarball itself.
+RUN npm install -g "$(node -p "require('./package.json').packageManager.split('+')[0]")"
+```
+
+Two ordering rules, both easy to get wrong:
+
+1. The derive-line must come **after** the `COPY` that puts `package.json` into the WORKDIR — it
+   reads that file.
+2. It must be repeated in **each** stage that runs `pnpm`. A global install in `deps` does not reach
+   `builder`.
+
+### Step 3: Drop the hardcoded version in CI
+
+**GitHub Actions** — remove the `version` input:
+
+```yaml
+- name: Install pnpm
+  uses: pnpm/action-setup@v6      # reads packageManager; no `with: version:`
+```
+
+**GitLab CI** (or any runner without the action) — use the same derive-line:
+
+```yaml
+before_script:
+  # Provision the exact pnpm pinned in package.json (single source of truth).
+  - npm install -g "$(node -p "require('./package.json').packageManager.split('+')[0]")"
+  - pnpm install --frozen-lockfile
+```
+
+### Step 4 (optional): Guard it with a test
+
+Copy `tests/unit/pnpm-pin-contract.spec.ts` from this repo and trim it to the files your project has.
+The value is not the assertions — it is that the next person who "helpfully" re-adds
+`with: version: 11` or a second `npm install -g pnpm@…` gets a red build instead of a silent drift
+that surfaces months later as an unreproducible container.
+
+---
+
+## Compatibility Notes
+
+| Pattern | Status |
+|---------|--------|
+| Any application code, decorator, service, or config using the framework | ✅ Unaffected — no runtime code changed |
+| **npm-mode** consumers (`@lenne.tech/nest-server` as a dependency) | ✅ Unaffected — `pnpm add …@11.29.1` and done |
+| **Vendor-mode** consumers (`src/core/` copied in) | ✅ Unaffected — `src/core/` is byte-identical to 11.29.0; a sync produces no delta |
+| The framework's `packageManager` pin leaking into your project | ✅ Impossible — the field is read only from the root manifest, never from a dependency |
+| Your project's `Dockerfile` still using `corepack enable` | ⚠️ Works on Node <= 24, **breaks on Node >= 25** — apply Step 2 |
+| Your CI passing both `with: version:` **and** having a `packageManager` field | ⚠️ Hard error on version mismatch — apply Step 3 |
+| Node version | ✅ Unchanged (`engines.node: ">= 22"`); the framework's own images stay on Node 24 LTS |
+| pnpm 10 or older as your project's package manager | ⚠️ `engines.pnpm: "^11.0.0"` warns (`EBADENGINE`); a hard failure only with `engine-strict=true` |
+
+---
+
+## Troubleshooting
+
+### `corepack: not found` in a Docker build or CI job
+
+You moved to a Node >= 25 image while your build still calls `corepack enable`. This is exactly the
+failure this release prevents — apply [Step 2](#step-2-replace-corepack-in-your-dockerfile). Do not
+"fix" it with `npm install -g corepack`: that reintroduces the indirection the derive-line removes.
+
+### Docker build fails with `TypeError: Cannot read properties of undefined (reading 'split')`
+
+The derive-line found a `package.json` **without** a `packageManager` field. Almost always a
+monorepo: in monorepo mode the build context is the workspace root, so `/app/package.json` is the
+**root** manifest — and the pin was only added to `projects/api/package.json`.
+
+Fix: add `packageManager` to the workspace **root** manifest (Step 1). Keeping the root and the API
+package on the same pin is the point — one pnpm builds the whole workspace.
+
+### `ERR_PNPM_BAD_PM_VERSION`, or the action reports multiple pnpm versions
+
+Two sources disagree about the version. Either your workflow still passes `with: version:` alongside
+a `packageManager` field (remove the input — [Step 3](#step-3-drop-the-hardcoded-version-in-ci)), or a
+stray `npm install -g pnpm@<other>` runs before the derive-line.
+
+### `EBADENGINE` / `ERR_PNPM_UNSUPPORTED_ENGINE` warning mentioning pnpm
+
+Unchanged from 11.29.0 — `engines.pnpm: "^11.0.0"` warns when installing with pnpm 10 or older.
+Upgrade with `npm i -g pnpm@11`, or pin your project via `packageManager` and let pnpm switch itself.
+The framework's *runtime* does not depend on pnpm; this concerns the install step only.
+
+### `EBADDEVENGINES` from npm or npx
+
+Something added a `devEngines.packageManager` block. npm and npx abort on it, and corepack rejects
+ranges inside it. Use `packageManager` (exact pin) plus `engines.pnpm` (soft range) instead — the
+contract test asserts `devEngines.packageManager` stays absent.
+
+---
+
+## Affected Files
+
+No core module changed in this release, so there is no module documentation to revisit. For
+completeness, the full change surface:
+
+| File | Change |
+|------|--------|
+| `package.json` | `packageManager` restored (exact pin + `sha512`); version → 11.29.1 |
+| `Dockerfile` | `corepack enable` removed; derive-line added to the `deps` and `builder` stages |
+| `.github/workflows/build.yml`, `publish.yml` | `with: version: 11` removed from `pnpm/action-setup` |
+| `tests/unit/pnpm-pin-contract.spec.ts` | **New** — 11 structural assertions + 1 CI-gated provisioning proof |
+| `spectaql.yml`, `FRAMEWORK-API.md` | Version bump only (kept in sync per the release process) |
+| `.claude/rules/package-management.md` | Documents the corepack-free pin contract |
+
+---
+
+## References
+
+- [Package Management Rules — fixed versions, overrides, the pnpm pin contract](../.claude/rules/package-management.md)
+- [Versioning Strategy — release process, `package.json` / `spectaql.yml` version sync](../.claude/rules/versioning.md)
+- Contract test: `tests/unit/pnpm-pin-contract.spec.ts`
+- [Migration Guide 11.28.1 → 11.29.0](./11.28.1-to-11.29.0.md) — previous release (introduced the `engines.pnpm` gate this guide keeps)
+- [Migration Guide 11.27.6 → 11.27.7](./11.27.6-to-11.27.7.md) — the pnpm 11 move, when corepack was still the mechanism
+- [nest-server-starter](https://github.com/lenneTech/nest-server-starter) (reference implementation)
+</content>
+</invoke>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lenne.tech/nest-server",
-  "version": "11.29.0",
+  "version": "11.29.1",
   "description": "Modern, fast, powerful Node.js web framework in TypeScript based on Nest with a GraphQL API and a connection to MongoDB (or other databases).",
   "keywords": [
     "node",
@@ -79,6 +79,7 @@
     "node": ">= 22",
     "pnpm": "^11.0.0"
   },
+  "packageManager": "pnpm@11.13.1+sha512.b2fc7683b8a6525414e7d13e1ba28caaddde96bf66ec540bfaeb7e702b81f3e0be4d1f295edf7f9fe0396740a8dce4509c582ddf79891f4543fea32d37645f25",
   "dependencies": {
     "@apollo/server": "5.5.1",
     "@as-integrations/express5": "1.1.2",