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.6.0 968f53dfa2
    Compare

    Onebox v33.6.0
    Release / build-and-release (push) Failing after 44m22s
    Details
    Stable

    philkunz released this 2026-10-04 07:37:54 +00:00 | 51 commits to main since this release

    2026-10-04 - 33.6.0

    Features

    • Bundle the Cloudly App Store template 1.17.0 for Cloudly 33.13.4 through @serve.zone/appstore 32.17.0, moved from 32.16.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.17.0 needs this release. The template pins the Cloudly 33.13.4 image index code.foss.global/serve.zone/cloudly@sha256:b1846a07c9818b5e77f4fd39951256088b3f57101b64695db7aa7ca35eb5ef5c and keeps the 1.16.0 runtime contract, minOneboxVersion 32.4.0 and upgrade flags; against 1.16.0 only its image and changelog differ. Cloudly 33.13.4 delivers the secret material of a run started through the WorkloadInit launcher again (Cloudly compared the run's pinned artifact with the approved one as JSON strings, so every launcher-delivered run's material, Corestore's MONGODB_URI included, was denied; it now compares the platform and both digests), remembers a successful WorkloadInit approval verification of an active artifact by its SHA-256 so a material request no longer waits for a registry verification each time, and answers a refused material request with { code: 'runtime-session-report-refused', reason }, a closed, value-free reason; since Cloudly 33.13.3 a node's session is pushed once per assignment revision instead of on every delivery pass. Cloudly 33.13.3 and 33.13.4 keep the data version 0.24.0, so an upgrade from 1.16.0 runs no data step. From 1.15.0 and every earlier template Cloudly still runs the forward-only 0.23.0 to 0.24.0 step corestore-control-token-state at its first start, after the earlier steps the older installs need, 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. Hosts read the migration-required, backup-before-upgrade, breaking and manual-review flags from the target version alone, so they stay set for every source version, and the template names the rollout order Cloudly 33.13.4 before Coreflow 33.2.0. 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.17.0 is the latest catalog version and prepares its upgrade from installs of 1.2.1 through 1.16.0, the latter on the Cloudly 33.13.2 image. App Store 32.17.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) and changes only the App Store entry. In pnpm-lock.yaml the install also moved the test-only containerarchive-legacy-index alias (@serve.zone/containerarchive 0.6.2) from @push.rocks/lik 6.4.2 to 6.4.4, a version already in the tree, so no package enters or leaves it; no entry was rewritten to SHA-1.
    Downloads