• Onebox v33.5.0
    Release / build-and-release (push) Failing after 27m52s
    Stable

    philkunz released this 2026-10-03 16:32:55 +00:00 | 53 commits to main since this release

    2026-10-03 - 33.5.0

    Features

    • Bundle the Cloudly App Store template 1.16.0 for Cloudly 33.13.2 through @serve.zone/appstore 32.16.0, moved from 32.15.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.16.0 needs this release. The template pins the Cloudly 33.13.2 image index code.foss.global/serve.zone/cloudly@sha256:e97c7768f845494b6d269709e56fccf6178519910d70ed3877a1368f3976e3d0 and keeps the 1.15.0 runtime contract and minOneboxVersion 32.4.0; against 1.15.0 only its image and changelog differ. Cloudly 33.11.0 moves the data version from 0.23.0 to 0.24.0: from 1.15.0 and every earlier template Cloudly runs the forward-only data step corestore-control-token-state at its first start, which records a Corestore control token stored before 33.11.0 as revision 1, after the earlier steps the older installs need (from 1.8.0 and earlier deployment-machine-user-grants from 0.22.0 to 0.23.0, from 1.6.0 and earlier runtime-session-protocol-offer from 0.21.0 to 0.22.0, and from 1.2.1 the 0.20.0 to 0.21.0 migration of Cloudly 33.0.0). The step has no inverse and every earlier Cloudly refuses the migrated data (DOWNGRADE_NOT_SUPPORTED), so stop Cloudly and take a verified backup (onebox backup create cloudly) before upgrading; a rollback is onebox backup restore <backup-id> of that backup, not an App Store downgrade, which the forward-only catalog gate refuses anyway. The migration-required, backup-before-upgrade, breaking and manual-review flags of the template therefore now hold for every source version, and it names the rollout order Cloudly 33.13.2 before Coreflow 33.2.0. Cloudly 33.11.0 through 33.13.2 let an administrator set the Corestore control token without an exec into Cloudly's container (setCorestoreControlToken, getCorestoreControlTokenState, servezone corestore set-control-token), retire a cluster node (retireClusterNode), keep a node's VPN membership across a protected-authority step that only adds, and keep the lease of a stopping workload until the node's stop receipt; the collections they need (Corestore control token state and receipts, node retirement rows and admissions, egress retirements, runtime slot abandonments) Cloudly installs at startup. From 1.14.0 or earlier the Cloudly 33.10.0 relay bearer export applies too. Onebox enforces only minOneboxVersion; the other flags and the template changelog are the operator's, as the Cloudly upgrade runbook states. The App Store upgrade test now checks that 1.16.0 is the latest catalog version and prepares its upgrade from installs of 1.2.1 through 1.15.0, the latter on the Cloudly 33.10.0 image. App Store 32.16.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 (505 packages, every one pinned by SHA-512, no tarball URL); besides the App Store it only marks @push.rocks/consolecolor 2.0.4, @push.rocks/smartdelay 3.1.0, @push.rocks/smarthash 3.3.0 and @push.rocks/webrequest 4.3.1 deprecated at unchanged versions, as the registry now reports them. In pnpm-lock.yaml the install also folded two development-only duplicates: @git.zone/tsdeno now resolves the project's @git.zone/tsbundle 3.1.3, so @git.zone/tsbundle 2.15.0, 3.1.0 and 3.1.2 and @push.rocks/smartcli 4.3.1 and 5.0.1 leave the tree, and the test-only containerarchive-legacy-index alias resolves @push.rocks/smartpromise 4.3.0; no entry was rewritten to SHA-1.

    Maintenance

    • Release tooling: @git.zone/tstest 7.1.0 (from 6.3.4; its breaking change, TapNodeTools.runCommand() output, is unused here), @git.zone/tswatch ^6.0.1 (from ^5.0.1; Onebox already builds with tsbundle 3), @git.zone/tsbuild ^5.1.2, @git.zone/tsbundle ^3.1.3 and @types/node 26.6.3; pnpm 12.7.0 and @git.zone/tsdeno ^1.14.1 are already current, and @types/node stays below 26.6.4 until it is seven days old.
    Downloads