@serve.zone/appstore 33.15.1 → 33.17.0

package/changelog.md

@@ -1,5 +1,29 @@
 # Changelog
 
+## 2026-10-21 - 33.17.0
+
+### Features
+
+- publish the Cloudly 1.29.9 and 1.30.5 templates on Cloudly 33.23.0 with its forward-only data step (cloudly)
+  - Add Cloudly app version 1.29.9, pinned to the Cloudly 33.23.0 multi-platform image index `code.foss.global/serve.zone/cloudly@sha256:73be2fb57ee6bf40f83569c677f381713a7ddcc38fedbb3f16a7d85fb1e6e33d` (tag `v33.23.0`), on 1.29.8's config with the image and the changelog changed: it keeps `CLOUDLY_BACKUP_CRON` `15 2 * * *`, `backupExclusions` for `runtime-logs/` and `requiresFeatures: ['storage.object-storage.backup-exclusions']`, and is the newest Cloudly target of a host that does not fulfil `storage.database.backup-exclusions`.
+  - Add Cloudly app version 1.30.5, 1.29.9 plus 1.30.0's `databaseBackupExclusions` for the six runtime log ledger collections and `requiresFeatures: ['storage.database.backup-exclusions', 'storage.object-storage.backup-exclusions']` (`declarationsOf: '1.29.9'` in `test/test.cloudlytemplates.node.ts`), and make it Cloudly's latest version; it is the upgrade target of 1.30.4, 1.30.3, 1.30.2, 1.30.1, 1.30.0, 1.29.9, 1.29.8 and every version 1.30.0 upgrades from.
+  - Cloudly 33.23.0 adds the forward-only data step `retire-stale-reconciliation-stages` (data version 0.32.0 to 0.33.0), which deletes the reconciliation records nothing reports again: every record of a kind only the Swarm-era Coreflow reconciler wrote and every `externalGateway` record of a route its service no longer declares. Cloudly 33.22.0, 33.21.4 and earlier refuse data version 0.33.0, so both templates keep the four upgrade flags and a return to 1.29.8, 1.30.4 or an earlier template means restoring the database backup taken before the upgrade.
+  - Cloudly 33.23.0 composes a service's status from the producers it runs (getServices for an administrator only), drops the Swarm-era Coreflow intake (`reportReconciliationStatus`, `reportDeploymentSnapshots`) and the dashboard summary's `deployments` count, adds delegated admin temp tokens and moves to `@serve.zone/interfaces` 32.61.0; it takes Cloudly 33.22.0, which no template ran (the scheduled `backup-all-services` task backs up each service on the node and cluster its data lives on and fails a run by name; `servezone service credential`). Neither release adds an environment variable or a setting or changes the Dockerfile or the `qenv.yml` requirements; both templates keep the Onebox minimum 33.8.0.
+
+## 2026-10-20 - 33.16.0
+
+### Features
+
+- publish the Cloudly 1.29.8 and 1.30.4 templates on Cloudly 33.21.4 with scheduled workload backups (cloudly)
+  - Add Cloudly app version 1.29.8, pinned to the Cloudly 33.21.4 multi-platform image index `code.foss.global/serve.zone/cloudly@sha256:e8e0f2b5a9e3d7aff4ba3201e358e99900b5c3792c24873b3dc0b3cb3f921439` (tag `v33.21.4`), on 1.29.7's config with the image, the changelog and one environment variable changed: it keeps `backupExclusions` for `runtime-logs/` and `requiresFeatures: ['storage.object-storage.backup-exclusions']`, declares no `databaseBackupExclusions`, and is the newest Cloudly target of a host that does not fulfil `storage.database.backup-exclusions` (Onebox 33.17.2), reached from 1.29.7 down to 1.28.3.
+  - Add Cloudly app version 1.30.4, 1.29.8 plus 1.30.0's `databaseBackupExclusions` for the six runtime log ledger collections and `requiresFeatures: ['storage.database.backup-exclusions', 'storage.object-storage.backup-exclusions']` (`declarationsOf: '1.29.8'` in `test/test.cloudlytemplates.node.ts`), and make it Cloudly's latest version; it is the upgrade target of 1.30.3, 1.30.2, 1.30.1, 1.30.0, 1.29.8 and 1.29.7 and of 1.29.6 down to 1.28.3.
+  - Both templates set `CLOUDLY_BACKUP_CRON` to `15 2 * * *` (plain, not required, no secret): Cloudly registers its `backup-all-services` task only when the variable is set, and no earlier template set it, so the databases of the workload services were never backed up on a schedule. Cloudly now backs them up daily at 02:15 UTC, clear of Onebox's `backup-archive-prune` at 03:00, and keeps the newest 24 backups of each service (`CLOUDLY_BACKUP_KEEP_LAST` default). A workload's object storage is not part of these backups (AGL-473). Onebox gives a key a service does not have yet the template's value on upgrade, so an upgraded Cloudly runs the schedule.
+  - Cloudly 33.21.4 is a fixes-only patch over 33.21.3: a launcher-environment secret file is owned by the identity the workload runs as, derived per target cluster from the spec's `runAs` and the image's `config.User` (AGL-459), and it moves to `@serve.zone/interfaces` 32.60.0 (external registry answers without the stored credential, partial service updates), with dashboard, deployment and node fixes. It adds no data step and keeps data version 0.32.0, no index, no collection and no setting, so the Onebox minimum stays 33.8.0 and the four upgrade flags stay set for the 0.32.0 step an upgrade from 1.29.6 or earlier runs.
+
+### Maintenance
+
+- release tooling: `@git.zone/tsrepo` 1.1.1
+
 ## 2026-10-20 - 33.15.1
 
 ### Fixes

package/dist_catalog/catalog.digest

@@ -1 +1 @@
-sha256:63ac7237f659e9a36a473f09c97ccd0dfef034221ac393952524f4a1ae329c7f
+sha256:fa1d470672b5b5d56b05dcf1f16ab395329a8b298e61f0d137e15a07c63d9a07