@tinycloud/cli 1.5.0-beta.17 → 1.5.0-beta.18
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/README.md +1 -0
- package/dist/index.js +2 -0
- package/dist/index.js.map +1 -1
- package/dist/legacy-entry.js +93 -30
- package/dist/legacy-entry.js.map +1 -1
- package/package.json +5 -5
- package/skills/tc-cli/REFERENCE.md +2 -0
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@tinycloud/cli",
|
|
3
|
-
"version": "1.5.0-beta.
|
|
3
|
+
"version": "1.5.0-beta.18",
|
|
4
4
|
"description": "TinyCloud CLI - manage data, delegations, and nodes from the terminal",
|
|
5
5
|
"author": "TinyCloud, Inc.",
|
|
6
6
|
"license": "EGPL",
|
|
@@ -35,11 +35,11 @@
|
|
|
35
35
|
"dependencies": {
|
|
36
36
|
"@tinycloud/share-sdk": "1.4.1-beta.0",
|
|
37
37
|
"@tinycloud/share-envelope": "1.3.1-beta.0",
|
|
38
|
-
"@tinycloud/node-sdk": "3.8.0-beta.
|
|
38
|
+
"@tinycloud/node-sdk": "3.8.0-beta.14",
|
|
39
39
|
"@tinycloud/node-sdk-wasm": "1.7.8",
|
|
40
|
-
"@tinycloud/sdk-core": "3.8.0-beta.
|
|
40
|
+
"@tinycloud/sdk-core": "3.8.0-beta.14",
|
|
41
41
|
"@tinycloud/sdk-services": "3.8.0-beta.9",
|
|
42
|
-
"@tinycloud/operations": "0.7.7-beta.
|
|
42
|
+
"@tinycloud/operations": "0.7.7-beta.13",
|
|
43
43
|
"chalk": "^5.3.0",
|
|
44
44
|
"commander": "^14.0.0",
|
|
45
45
|
"jsdom": "26.1.0",
|
|
@@ -48,7 +48,7 @@
|
|
|
48
48
|
"siwe": "^3.0.0"
|
|
49
49
|
},
|
|
50
50
|
"devDependencies": {
|
|
51
|
-
"@tinycloud/courier": "0.3.3-beta.
|
|
51
|
+
"@tinycloud/courier": "0.3.3-beta.12",
|
|
52
52
|
"@tinycloud/replica": "0.4.0-beta.3",
|
|
53
53
|
"@types/node": "^20",
|
|
54
54
|
"tsup": "^8.0.0",
|
|
@@ -104,6 +104,8 @@ warning that revocation signs you out. After the node confirms that exact CID,
|
|
|
104
104
|
the CLI runs its normal durable logout, removes the restorable session and key,
|
|
105
105
|
and blocks implicit reauthentication. Unrelated CIDs do not sign you out.
|
|
106
106
|
|
|
107
|
+
From a delegate (agent) profile, `delegation list --granted` lists the delegations that profile's own key issued: every page of the node's issued-delegations listing, each with its `status`, sorted by delegation ID rather than by date (the output's `note` says so). A node that does not offer the listing yet answers `ISSUED_DELEGATIONS_UNAVAILABLE` (exit 7). `delegation revoke <cid>` from a delegate profile revokes a delegation its own key issued with a revocation signed by that key, so it needs no revoke grant from the owner. Revoking one that's already revoked also succeeds. A delegation the key did not issue is refused with the node's message (`REVOKE_UNAUTHORIZED`, exit 5). A chain too long for the node to check right now answers `CHAIN_TOO_DEEP` (exit 7); retry later. Owner profiles behave as described above.
|
|
108
|
+
|
|
107
109
|
A grant the owner signed through `auth grant` can be revoked from any of the owner's profiles, including one that never recorded it (another CLI profile or machine). When this profile has no local record of the CID, the CLI reads the owner's delegation records on the node and uses that record's space only if the grant was issued by the signed-in owner (the issuer is the owner or the signed-in session key, or a key that holds a delegation recorded on the node whose own issuer is, in turn, one of those: any holder along such an owner-rooted chain counts, up to 8 hops) and every space it covers is one plain space id (`tinycloud:pkh:eip155:<chain>:<address>:<name>`) that belongs to that owner. The lookup reads at most 5,000 records (pages of 100; a larger page is refused) and refuses rather than decides on a partial list. A CID the node does not list, one issued by someone else, a space the owner does not hold, or an ambiguous record is refused (`RAW_RECAP_RESOURCE_UNSUPPORTED`, "this CLI profile has no record of this grant and the node's record does not match the signed-in owner"). An OpenKey owner uses the same space-scoped request as for a locally recorded grant; OpenKey profiles hold no wallet signer, so there is no wallet-signed revoke for them. After the revoke, the agent's next call is refused (`GRANT_REVOKED`, exit 5, the same as `tc replica`: "This grant was revoked. Ask the owner for a new grant") as soon as the node has recorded it.
|
|
108
110
|
|
|
109
111
|
`tinycloud auth import` stores delegations in `additional-delegations.json`. Every replay path installs only a grant with a locally verified proof and a binding containing its signed authority; unbound and proof-less grants never install, including while migration is deferred. [AUTH.md](AUTH.md#imported-delegations-and-their-request-bindings) covers migration and recovery.
|