serve.zone/onebox
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 82 Wiki Activity

82 Releases 305 Tags

RSS Feed
  • v33.13.0 10fa661fd2
    Compare

    Onebox v33.13.0
    Release / build-and-release (push) Failing after 19m23s
    Details
    Stable

    philkunz released this 2026-10-07 14:59:10 +00:00 | 32 commits to main since this release

    2026-10-07 - 33.13.0

    Features

    • Bundle the Cloudly App Store template 1.26.0 for Cloudly 33.17.1 through @serve.zone/appstore 32.26.0, moved from 32.25.0 in package.json, pnpm-lock.yaml and the binary's deno.lock. Onebox reads the App Store from the catalog this package bundles, so onebox appstore upgrade cloudly --version 1.26.0 needs this release. The template pins the Cloudly 33.17.1 image index code.foss.global/serve.zone/cloudly@sha256:41ec10edac38281acd084c1e034bbd090a0f684a31d467b25c8787ab73d75fc5 and keeps minOneboxVersion 33.8.0, so Onebox 33.7.0 and earlier still refuse the upgrade with App requires Onebox >= 33.8.0; current version is <version>. 1.26.0 differs from 1.25.0 only in the image and changelog. Cloudly 33.17.0, which template 1.25.0 pins, crash-looped at its first start on a database holding Pallet-era nodes: its first data step cluster-node-hostname-intent (0.25.0 → 0.26.0) was refused before its first write, because it used the node and cluster models, which startup has not prepared while it runs the data steps. Cloudly 33.17.1 runs that step on the stored documents directly. The migration ledger does not advance past a failed step, so a 1.25.0 install whose first start failed stayed at data version 0.25.0 and upgrades to 1.26.0 normally. Cloudly 33.17.1 keeps the data steps of 33.17.0 from 0.25.0 to 0.28.0 (cluster-node-hostname-intent, deployment-operation-route-evidence, service-secret-target-predecessor), so every upgrade runs a data step at Cloudly's first start, which every Cloudly before 33.17.0 refuses (DOWNGRADE_NOT_SUPPORTED); an upgrade from 1.19.0 or earlier first runs runtime-log-attempts. Stop Cloudly and take a verified backup (onebox backup create cloudly) before upgrading; a rollback is onebox backup restore <backup-id> of that backup. Onebox enforces only minOneboxVersion; the other flags and the template changelog are the operator's. The App Store upgrade test now prepares the 1.26.0 upgrade from installs of 1.2.1 through 1.25.0 on Onebox 33.8.0, checks that 1.26.0 differs from 1.25.0 only in its image and changelog, and checks that Onebox 33.7.0 refuses it from 1.19.0 with that exact message. App Store 32.26.0 keeps @serve.zone/interfaces 32.42.0, so no other serve.zone package moves. deno.lock was re-resolved from https://registry.npmjs.org/ after a build and changes only the App Store entry, pinned by SHA-512. In pnpm-lock.yaml only the App Store entry changes, pinned by SHA-512.
    Downloads