wendkeep 0.57.1 → 0.57.2

package/CHANGELOG.md

@@ -4,6 +4,22 @@ All notable changes to **wendkeep** are documented here. Format based on
 [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); this project follows
 [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.57.2] — 2026-07-25
+
+### Fixed
+
+- **O README deixa de recomendar um `pnpm add` que não atualiza.** A seção "Atualizar"
+  mandava rodar `pnpm add -D -w wendkeep@latest`. Medido num projeto pnpm limpo, sem
+  configuração alguma: o comando devolveu `+ wendkeep 0.49.0 (0.57.1 is available)` e saiu 0.
+  O `minimumReleaseAge` de 24h é **default do pnpm 11**, não config do projeto, e ele não
+  recusa o pacote recente — instala o anterior em silêncio, com o `(X.Y.Z is available)` como
+  única pista. Quem seguia o README ficava na versão velha achando que tinha atualizado. O
+  bloco pnpm passa a mostrar a versão exata com `--config.minimumReleaseAge=0`, e o `@latest`
+  aparece como armadilha nomeada. A nota também corrige quem escreve a exceção: o
+  `minimumReleaseAgeExclude` do `pnpm-workspace.yaml` é **manual** — o pnpm não escreve essa
+  linha, e sem ela o `pnpm install` do CI falha com
+  `ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION` até a versão completar 24h. Vale nos dois idiomas.
+
 ## [0.57.1] — 2026-07-25
 
 ### Fixed

package/README.en.md

@@ -124,16 +124,28 @@ The install stays outside `sync` on purpose: a running process cannot replace it
 keep going — the code in memory would still be the old one.
 
 In a **pnpm** monorepo the install command differs (`npm` in a pnpm repo fails with
-`Cannot read properties of null (reading 'matches')`):
+`Cannot read properties of null (reading 'matches')`) and the version must be **exact**:
 
 ```bash
-pnpm add -D -w wendkeep@latest && npx --no-install wendkeep sync --project . --yes
+pnpm add -D -w wendkeep@X.Y.Z --config.minimumReleaseAge=0 && npx --no-install wendkeep sync --project . --yes
 ```
 
-> pnpm refuses packages published in the last ~24h (`minimumReleaseAge`, a supply-chain
-> guard). If you just published and need it now, ask for the exact version with
-> `--config.minimumReleaseAge=0` and record the exception under `minimumReleaseAgeExclude`
-> in `pnpm-workspace.yaml` — otherwise CI's `pnpm install` starts failing.
+> **Do not ask pnpm for `wendkeep@latest`.** pnpm 11 ignores packages published in the last
+> 24h by default (`minimumReleaseAge`, a supply-chain guard) — and it does not complain: it
+> installs the previous version, exits 0, and the only hint is a quiet `(X.Y.Z is available)`
+> in the output. You end up on the old version thinking you upgraded. Check with
+> `npx wendkeep --version`.
+>
+> After installing, record the exception in `pnpm-workspace.yaml` — **pnpm does not write
+> that line for you**:
+>
+> ```yaml
+> minimumReleaseAgeExclude:
+>   - wendkeep@X.Y.Z
+> ```
+>
+> Without it, CI's `pnpm install` fails with `ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION` until
+> the version turns 24h old.
 
 Restart Codex and Claude Code afterwards — the generated skills are read at startup.
 

package/README.md

@@ -124,16 +124,28 @@ The install stays outside `sync` on purpose: a running process cannot replace it
 keep going — the code in memory would still be the old one.
 
 In a **pnpm** monorepo the install command differs (`npm` in a pnpm repo fails with
-`Cannot read properties of null (reading 'matches')`):
+`Cannot read properties of null (reading 'matches')`) and the version must be **exact**:
 
 ```bash
-pnpm add -D -w wendkeep@latest && npx --no-install wendkeep sync --project . --yes
+pnpm add -D -w wendkeep@X.Y.Z --config.minimumReleaseAge=0 && npx --no-install wendkeep sync --project . --yes
 ```
 
-> pnpm refuses packages published in the last ~24h (`minimumReleaseAge`, a supply-chain
-> guard). If you just published and need it now, ask for the exact version with
-> `--config.minimumReleaseAge=0` and record the exception under `minimumReleaseAgeExclude`
-> in `pnpm-workspace.yaml` — otherwise CI's `pnpm install` starts failing.
+> **Do not ask pnpm for `wendkeep@latest`.** pnpm 11 ignores packages published in the last
+> 24h by default (`minimumReleaseAge`, a supply-chain guard) — and it does not complain: it
+> installs the previous version, exits 0, and the only hint is a quiet `(X.Y.Z is available)`
+> in the output. You end up on the old version thinking you upgraded. Check with
+> `npx wendkeep --version`.
+>
+> After installing, record the exception in `pnpm-workspace.yaml` — **pnpm does not write
+> that line for you**:
+>
+> ```yaml
+> minimumReleaseAgeExclude:
+>   - wendkeep@X.Y.Z
+> ```
+>
+> Without it, CI's `pnpm install` fails with `ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION` until
+> the version turns 24h old.
 
 Restart Codex and Claude Code afterwards — the generated skills are read at startup.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wendkeep",
-  "version": "0.57.1",
+  "version": "0.57.2",
   "description": "A persistent-memory harness for AI coding agents on your Obsidian vault: turn-by-turn session capture plus a native, zero-dependency spec→change→verify→archive loop (sensor-gated, independent verdict, mutation discrimination). Local-first, agent-agnostic (Claude Code, Codex, Cursor…).",
   "type": "module",
   "bin": {
@@ -49,6 +49,6 @@
     "url": "https://github.com/rogersialves/wendkeep/issues"
   },
   "devDependencies": {
-    "wendkeep": "^0.54.0"
+    "wendkeep": "^0.57.1"
   }
 }