chore(tcloud): release Sandbox evidence compatibility - #63
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
tangletools
left a comment
There was a problem hiding this comment.
✅ Auto-approved PR — 6095eff7
Blanket team auto-approval is intentional. The merge gates are CI and codex-p1.
No automated review runs on this PR. This approval rests on the rule above alone.
tangletools · auto-approval · reason: blanket_auto_approve · 2026-09-30T04:52:18Z
|
Independent cohort review APPROVED at exact source 6095eff. The review confirms d708870..HEAD changes only standalone version 0.8.0, Sandbox >=0.58.4 <0.59.0, and normal generated lock resolution. Standalone reachable dependencies exclude the separate old tcloud-agent SDK cohort. No source finding remains. Exact-head sdk CI is SUCCESS, all normal local release checks and hooks passed, and main merges cleanly. The final Lab singleton claim belongs to its fresh installed consumer. The release source claim remains the standalone TCloud package. Proceeding with the maintained merge/tag publisher under standing owner authorization. |
Change
Release @tangle-network/tcloud 0.8.0 with Sandbox >=0.58.4 <0.59.0.
The lockfile resolves the now-public Sandbox 0.58.4 artifact.
This provides the compatible transport dependency for the current research cohort.
Proof
The separate tcloud-agent package retains its earlier SDK dependency.
The compatibility claim applies to the standalone TCloud package and its consumer graph.
Publication
The maintained release workflow publishes tag @tangle-network/tcloud@0.8.0 after this commit is on main.
Drew configured the npm trusted publisher; the saved page shows tangle-network/tcloud, release.yml, and npm publish permission.
Publication uses that existing workflow connection.