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

82 Releases 305 Tags

RSS Feed
  • v32.21.0 83e52efb16
    Compare

    v32.21.0
    Release / build-and-release (push) Failing after 11m46s
    Details
    Stable

    philkunz released this 2026-09-29 06:55:18 +00:00 | 90 commits to main since this release

    Do not install v32.21.0. Its binaries cannot reach the Docker socket (invalid proxy url under Deno 2.9.6 and later) and crash-loop at start. Use v32.21.1, which fixes this.

    2026-09-29 - 32.21.0

    Features

    • Bundle the Cloudly App Store template 1.10.0 for Cloudly 33.7.0 through @serve.zone/appstore 32.10.0, moved from 32.9.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.10.0 on a host running template 1.2.1, 1.3.0, 1.4.0, 1.5.0, 1.6.0, 1.7.0, 1.8.0 or 1.9.0 needs this release. The template pins the Cloudly 33.7.0 image index code.foss.global/serve.zone/cloudly@sha256:0b492a2511643981f003f1424715cf5abcdf39767fe5c995ad036a31b219f61e, keeps the 1.9.0 runtime contract (environment, both root-only secret files, platform OIDC, health check) and requires Onebox 32.4.0; against 1.9.0 only its image and changelog differ. Cloudly 33.7.0 lets a fresh greenfield service adopt a legacy service's Corestore database and bucket with their data through successorServiceId, refuses a deployment reservation whose release tag the service registry already holds a digest for with DEPLOYMENT_RELEASE_TAG_OCCUPIED, refuses an administrator's push to a reserved release tag, and pushes a platform binding's status back to its cluster relay only when it changed. It stores the adoption claims in a new collection and keeps the data version 0.23.0, so from 1.9.0 there is no data step. The template still marks the upgrade migration-required, backup-before-upgrade, breaking and manual-review, because hosts read these flags from the target version alone: from 1.8.0 and every earlier template Cloudly runs the forward-only data step deployment-machine-user-grants from 0.22.0 to 0.23.0 at its first start, from 1.6.0 and earlier the step runtime-session-protocol-offer from 0.21.0 to 0.22.0 before it, and from 1.2.1 the 0.20.0 to 0.21.0 migration of Cloudly 33.0.0 first; no step has an inverse, so stop Cloudly and take a verified backup before upgrading, and from 1.7.0 and earlier switch every username and password deployer to a machine-user token first. Let no deployment run while Cloudly upgrades. The template changelog carries forward the notes of the earlier templates, with the rollout order Cloudly 33.7.0 before Coreflow 33.2.0 from 1.4.0 and earlier. 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.10.0 is the latest catalog version and prepares its upgrade from installs of 1.2.1 (Cloudly 32.9.1 image, as central runs), 1.3.0, 1.4.0, 1.5.0, 1.6.0, 1.7.0, 1.8.0 and 1.9.0 (Cloudly 33.0.0, 33.1.0, 33.2.0, 33.3.0, 33.4.0, 33.5.0 and 33.6.0 images). App Store 32.10.0 still pins @serve.zone/interfaces 32.3.0, so no other runtime package moves.

    Maintenance

    • @design.estate/dees-catalog ^16.6.0 → ^16.12.0 in package.json and pnpm-lock.yaml, with @design.estate/dees-element 3.4.0 (from 3.3.0) through it; @serve.zone/catalog 33.0.0 (^16.4.0) resolves the same single copy of each, and the lockfile keeps the sha512 integrity of every package. No Onebox or @serve.zone/catalog view sets frameless or uses dees-stepper, dees-dashboardgrid or dees-input-list, so the transparent frameless surface of 16.12.0 and the removed stepper scroller/setScrollStatus() change no dashboard view.
    • Release tooling: the pinned Deno moves from 2.9.4 to 2.9.7, the release the other serve.zone binaries (Pallet, Spark, dcrouter) build with, in .smartconfig.json (denoVersion, which tsdeno compile enforces), the release workflow (the Deno toolchain and the seeded x64 and arm64 denort runtimes, each with the SHA-256 published with v2.9.7), binary/verify-runtime-cache.mjs and the readme. deno.lock stays as it is: Deno 2.9.7 checks every locked tarball origin against the configured registry, and Onebox's .npmrc names the same registry the lock records, so the frozen runtime graph warms and verifies unchanged (502 locked packages). The restore helper of test/corestore-backup.node.ts keeps its minimum of Deno 2.9.4, which is not the compile pin. The @git.zone/* build, test and release tools are already at their current releases; pnpm 12.6.0 and @types/node 26.6.3 still wait for the seven-day rule.
    • Release tooling: @git.zone/tsrun ^3.0.1 → ^3.0.2, which no longer loads two modules it never used, so every tsrun process starts about a second sooner.
    Downloads