@proulr/rosetta 0.1.2 → 0.1.3

package/docs/ROSETTA.md

@@ -210,7 +210,17 @@ Workflow: [`.github/workflows/publish-npm.yml`](../.github/workflows/publish-npm
 4. Workflow filename: `publish-npm.yml`
 5. Environment: vazio
 
-Sem Trusted Publisher, o job `publish` falha (404/401). Depois do publish, consumers usam `"@proulr/rosetta": "^0.1.1"`.
+Sem Trusted Publisher, o job `publish` falha (404/401) na 1ª vez — use `NPM_TOKEN` Automation no bootstrap. Consumers usam `"@proulr/rosetta": "^0.1.2"` (registry).
+
+### Version sync (pre-commit)
+
+Ao commit no Rosetta com mudança de source, o hook chama `../scripts/proulr-bump-and-sync-deps.mjs` (igual contract/core):
+
+1. Bump patch em `package.json`
+2. Atualiza `^versão` em app + BFFs que dependem de `@proulr/rosetta`
+3. Roda `npm install` nesses consumers
+
+Manual: `npm run version:sync` (com changes staged). `PROULR_BUMP_PUBLISH=1` publica no npm antes do sync.
 
 ---
 

package/docs/npm-publish-cicd.md

@@ -45,6 +45,10 @@ O workflow já tem `id-token: write`. Com Trusted Publisher configurado, o publi
 
 ## Consumidores (app / BFFs)
 
-```bash
-npm install @proulr/rosetta@^0.1.2
+Dependência do registry (não `file:`):
+
+```json
+"@proulr/rosetta": "^0.1.2"
 ```
+
+No commit do Rosetta, o pre-commit (`scripts/proulr-bump-and-sync-deps.mjs`) bumpa a versão e atualiza sozinho os `package.json` + `npm install` dos siblings.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@proulr/rosetta",
-  "version": "0.1.2",
+  "version": "0.1.3",
   "type": "module",
   "main": "./src/index.ts",
   "types": "./src/index.ts",