@authorbot/domain 0.1.34 → 0.1.35
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +27 -0
- package/package.json +2 -2
package/CHANGELOG.md
CHANGED
|
@@ -9,6 +9,33 @@ Every published package shares this version. A tag builds, tests, and publishes
|
|
|
9
9
|
all of them together, so `@authorbot/cli@0.1.15` and `@authorbot/api@0.1.15` are
|
|
10
10
|
always the same commit.
|
|
11
11
|
|
|
12
|
+
## 0.1.35
|
|
13
|
+
|
|
14
|
+
- **Legacy agent-token requests now maintain the canonical projection.** The
|
|
15
|
+
compatibility `{scopes}` request remains legacy-authoritative, but every new
|
|
16
|
+
token also records the exact safe capability translation. Control-plane
|
|
17
|
+
scopes never enter that projection. This dual-write Worker must be deployed
|
|
18
|
+
and verified before the one-shot legacy-row backfill ships in v0.1.36.
|
|
19
|
+
- **The upgrade helper now repairs a stale local toolchain before changing a
|
|
20
|
+
book.** Forward upgrades hand off to the exact target CLI in a throwaway
|
|
21
|
+
install when `node_modules` does not match the repository pin. That target
|
|
22
|
+
aligns the CLI and API packages, regenerates the lockfile, and preserves the
|
|
23
|
+
child exit code and JSON output. Interrupted same-version installs are
|
|
24
|
+
repaired through a normal reviewable pull request, with migration baselines
|
|
25
|
+
accepted only from coherent committed CLI lock evidence. Dry runs regenerate
|
|
26
|
+
and verify the lockfile in a throwaway copy. Windows launches npm, npx, and
|
|
27
|
+
Wrangler through validated JavaScript entry points under the current Node
|
|
28
|
+
executable, without enabling a command shell. Exact `--to` targets require
|
|
29
|
+
no registry metadata lookup; implicit discovery uses npm's configured
|
|
30
|
+
offline cache, registry, userconfig, and authentication. Existing helpers
|
|
31
|
+
from before 0.1.35 still need one explicit
|
|
32
|
+
`npx --yes @authorbot/cli@0.1.35 upgrade --to 0.1.35` launch; ordinary
|
|
33
|
+
`npx authorbot upgrade` self-bootstraps after that.
|
|
34
|
+
- This is a focused capability-writer-gate and upgrade-safety release. It adds
|
|
35
|
+
no D1 or book-format migration. The Phase 3B backfill is reserved for
|
|
36
|
+
v0.1.36 after this Worker is verified; Phase 3C legacy retirement remains a
|
|
37
|
+
deliberately separate later release.
|
|
38
|
+
|
|
12
39
|
## 0.1.34
|
|
13
40
|
|
|
14
41
|
- **The full editorial workflow is now available from the site.** Editors can
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@authorbot/domain",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.35",
|
|
4
4
|
"description": "Pure domain logic for Authorbot: role/scope authorization, annotation and Git-operation state machines, command validators, and token/session value rules (Phase 2 contract section 3)",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"authorbot",
|
|
@@ -40,7 +40,7 @@
|
|
|
40
40
|
],
|
|
41
41
|
"dependencies": {
|
|
42
42
|
"zod": "^4.0.0",
|
|
43
|
-
"@authorbot/schemas": "0.1.
|
|
43
|
+
"@authorbot/schemas": "0.1.35"
|
|
44
44
|
},
|
|
45
45
|
"devDependencies": {
|
|
46
46
|
"@types/node": "^22.0.0",
|