• v34.3.0 Stable

    philkunz released this 2026-11-22 11:43:14 +00:00 | 4 commits to main since this release

    Downloads
  • v34.2.0 Stable

    philkunz released this 2026-11-18 14:53:38 +00:00 | 9 commits to main since this release

    Downloads
  • v34.1.1 Stable

    philkunz released this 2026-11-16 12:37:55 +00:00 | 19 commits to main since this release

    Downloads
  • v34.1.0 Stable

    philkunz released this 2026-11-15 11:37:52 +00:00 | 21 commits to main since this release

    Downloads
  • v34.0.0 Stable

    philkunz released this 2026-11-15 04:13:15 +00:00 | 24 commits to main since this release

    Downloads
  • Onebox v33.17.2
    Release / build-and-release (push) Failing after 24m9s
    Stable

    philkunz released this 2026-10-14 21:44:40 +00:00 | 72 commits to main since this release

    2026-10-14 - 33.17.2

    Fixes

    • Pin the platform Corestore 32.2.7 by its multi-platform image index code.foss.global/serve.zone/corestore@sha256:73ebbfecc33f52022249bbbbdaef331c31b8bfaf3cd2de23cf58b874ef821334 (linux/amd64 and linux/arm64), moved from 32.2.5 (sha256:a6a702f04320e15198a16a309dd939af927d3bcd74d14d92b0ce3f44526a3e7d) in ts/platform-images.ts, and declare it as oneboxCorestorePinnedRelease 32.2.7. Corestore 32.2.7 is a maintenance release of the 32.2 line that serves object storage from @lossless.org/objectstorage 10.7.1 instead of 10.3.1 (through 32.2.6, which brought 10.7.0): reads no longer queue behind bucket listings. A listing held the engine-wide object gate while it walked and sorted the whole bucket, so every GET and HEAD on every bucket waited for it; a listing now holds a per-bucket gate that blocks only writes to the bucket it lists, the engine-wide object migration gate is held only for the legacy-layout reconciliation before the walk, and the walk covers only the keys its prefix and cursor reach. On central this removes the 6–25 s registry read stalls that pushed Cloudly deploy preflights past their deadlines. Through 10.7.0 workloads also get CopyObject read authorization on the source, durable staged writes, UploadPartCopy and disabled Nagle's algorithm (Corestore 32.2.6 changelog). The NoSQLDB engine stays 10.10.0 and the object layout is unchanged, so 32.2.5 to 32.2.7 adds no one-way step: 32.2.5 serves a pool 32.2.7 wrote, and the movers' restore to 32.2.5 holds. One rollback condition applies: a write of a new key that a crash interrupts leaves a staged directory in .smartstorage/staging/v1/ that 32.2.5's objectstorage 10.3.1 refuses at startup, so start and stop 32.2.7 once before rolling back to 32.2.5; if 32.2.7 cannot start, back up the root first, then remove only the *.object.tmp.leaf directories there, which hold payloads that were never published (Corestore 32.2.6 changelog). A completed engine conversion keeps running the image its journal names, so after the binary upgrade it still runs 32.2.5 until onebox migration corestore-engine --replace-completed-target-image moves it, and a native owner until --replace-native-target-image does; both admit 32.2.5 to 32.2.7 as a newer release of the same major, read from both images' release labels; the 32.2.7 index states 32.2.7 in its org.opencontainers.image.version and version labels on both platforms. An owner still on 32.2.4 or earlier crosses the one-way first start of NoSQLDB 10.10.0 with this move as it did with 32.2.5, so take a block-level snapshot of its Corestore volume with the services stopped first. The completed-target replacement test now runs the move from the 32.2.5 index with this release's own pin, and the backup exclusion tests run against objectstorage 10.7.1, the engine of the pinned Corestore. The change adds no startup data migration.

    Maintenance

    • release tooling: @git.zone/tstest 8.0.0, @git.zone/tsbundle 3.3.0 (pnpm 12.10.1 and @types/node 26.6.4 stay: pnpm 12.11.2 and @types/node 26.6.5 are younger than the 7-day release-age rule; @git.zone/tsdeno stays 1.15.0 until the binary moves from Deno to a Node single executable application, owner decision 2026-10-14)
    Downloads
  • Onebox v33.17.1
    Release / build-and-release (push) Failing after 25m30s
    Stable

    philkunz released this 2026-10-14 09:59:44 +00:00 | 76 commits to main since this release

    2026-10-14 - 33.17.1

    Fixes

    • A backup applies the backup-exclusion declaration the App Store catalog makes for the image the service runs, not only the one its installed version declares. 33.17.0 applied an upgrade target's declaration only when the target pinned the installed image digest, and the installed snapshot's otherwise; a service installed from a version that predates its app's declaration (Cloudly 1.28.3, which declares nothing, while 1.28.5 pins the identical image and declares runtime-logs/) was exported in full before an upgrade to a version on another image, so a bucket holding more than 100,000 log objects refused the pre-upgrade backup and blocked the upgrade. Whether data is non-backup data is a property of the app's code, so a backup now applies, in order: the upgrade target's declaration when it pins the installed image digest (unchanged); the declaration of the active catalog's versions of the app that pin exactly the installed image digest and are not withdrawn and interpretable by this Onebox, the newest by semver when they declare differently (never merged; opaque branch versions that disagree are not ordered, so none of them applies); a version on that image that needs App Store features this Onebox does not support (the feature gate of the install-target judgement) or whose storage config it cannot normalize is skipped and named in the record, never failing the backup; the installed snapshot's declaration; otherwise none, a full export with the reason recorded, as before. The backup row and snapshot tag dataExclusion and the onebox backup create line name the basis, e.g. declared by cloudly@1.28.5 for the installed image sha256:… of cloudly@1.28.3 in App Store catalog revision 12; the newest of 2 catalog versions on that image, which declare differently (cloudly@1.28.5, cloudly@1.28.3), applies; the upgrade target cloudly@1.29.1 runs another image digest. Restores are unchanged, and the feature id stays storage.object-storage.backup-exclusions.
    Downloads
  • Onebox v33.17.0
    Release / build-and-release (push) Failing after 12m19s
    Stable

    philkunz released this 2026-10-14 00:42:17 +00:00 | 79 commits to main since this release

    2026-10-14 - 33.17.0

    Features

    • Backups leave out the object-storage data an App Store version declares as non-backup data (backupExclusions, @serve.zone/interfaces 32.56.0), such as Cloudly's workload logs under runtime-logs/: a restore brings back state, not past logs. The declaration is read from the installed template snapshot, normalized by @serve.zone/appstore 33.6.0, and legacy-s3 names the service's one Corestore bucket. The bucket is listed with Delimiter='/', skipping a declared prefix without listing anything under it, so an excluded subtree costs one entry of its parent's listing on an objectstorage that walks the whole bucket for every list request; the 100,000-object and 16 MiB manifest caps count included objects only. Every bucket is now listed before the archive ingest starts, so the ingest's idle timeout never waits on a listing, and closing the backup manager (daemon shutdown) aborts that listing. The bucket manifest names the prefixes in excludedKeyPrefixes (written only when something was left out, so a backup without exclusions keeps the shape earlier releases restore); the backup row and snapshot tag dataExclusion record which version's declaration applied and why, and onebox backup import derives the same record from the imported bucket manifests (origin: 'import'); a restore logs the prefixes it does not restore and deletes nothing. An App Store service without a snapshot of its version is exported in full, with the reason recorded. onebox backup create <service> --upgrade-target <version> takes a backup for an upgrade and applies the target version's declaration when the target pins the installed version's image digest, the installed version's otherwise. Onebox advertises storage.object-storage.backup-exclusions, so catalog versions that declare exclusions become installable and upgradable; the exclusion applies to the legacy-s3 platform-resource bucket, and services with named object-storage requests stay refused for backup. The canonical storage handoff of @serve.zone/appstore 33.6.0 carries backupExclusions; a handoff a service or a backup saved before it has none, which Onebox reads as no declaration, so existing services and earlier backups keep validating.

    Fixes

    • A backup whose ContainerArchive ingest is aborted fails by name instead of ending the daemon. When an item's socket fell silent, ContainerArchive destroyed the item's stream with Ingest timed out after 300000ms without socket activity; the bundle passed that on to its tar pack, which destroyed the entry waiting in it with the same error. Entries added from bytes in memory (addBytes, such as an S3 bucket's manifest.json, a Valkey export or a Corestore receipt), directory and link entries, and the documents of a backup's OCI image layout had no listener on that entry stream, so the error was an uncaught exception: onebox backup create lost the daemon (exit 1, systemd restart) and the CLI saw Onebox control socket closed without a response. Every such entry now goes through one function (addTarEntry) that listens on it and rejects with the error, so the backup fails with it and the daemon keeps running. The same class of unheard stream errors is closed on the other backup and restore paths: a bundle stopped before anything read it (a download export refused by staging, or whose output file exists), an image layer opened after its layout was destroyed (now closed), an image archive that ends inside a skipped entry, a download export's output file (now opened and its header written through a file handle), restore streams that were opened before their directory was created, and the MariaDB and ClickHouse restore inputs, which are now opened when the restore reads them.

    Maintenance

    • release tooling: pnpm 12.10.1 (@git.zone/tsdeno stays 1.15.0: its 2.x migration ships as its own release, owner decision 2026-10-13)
    Downloads