@serve.zone/appstore 33.17.0 → 33.18.0

package/changelog.md

@@ -1,5 +1,18 @@
 # Changelog
 
+## 2026-10-22 - 33.18.0
+
+### Features
+
+- publish the Cloudly 1.29.10 and 1.30.6 templates on Cloudly 33.23.2 (cloudly)
+  - Add Cloudly app version 1.29.10, pinned to the Cloudly 33.23.2 multi-platform image index `code.foss.global/serve.zone/cloudly@sha256:cd0808e1fa4fdcf49742ac527480013ca506eb653fea4f82a86de546d1186876` (tag `v33.23.2`), on 1.29.9'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.6, 1.29.10 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.10'` in `test/test.cloudlytemplates.node.ts`), and make it Cloudly's latest version; it is the upgrade target of 1.30.5, 1.30.4, 1.30.3, 1.30.2, 1.30.1, 1.30.0, 1.29.10, 1.29.9 and every version 1.30.0 upgrades from.
+  - Cloudly 33.23.2 is a fixes-only patch over 33.23.0 and takes 33.23.1, which no template ran: one service whose status Cloudly cannot compose (a stored plan, rollout status or newest deployment operation that violates the contract, such as a plan written before it carried `releaseTag` and `operationId`) gets a failed status with one `composition` stage that names the violation instead of failing `getServices`, `getServiceById` and the MCP `cloudly_list_services` tool for every service; `servezone service credential ensure` takes over a legacy operator-managed `SERVEZONE_PLATFORM_AUTHORIZATION` in the same transaction (it revokes every legacy version that could still be issued; the legacy user token itself is not revoked automatically). Neither release adds a data step, an environment variable, a setting, a collection or an index or changes the Dockerfile or the `qenv.yml` requirements; both templates keep the Onebox minimum 33.8.0 and the four upgrade flags, because an upgrade from 1.29.8, 1.30.4 or earlier still runs the forward-only data step `retire-stale-reconciliation-stages` (data version 0.32.0 to 0.33.0).
+
+### Maintenance
+
+- Release tooling: pnpm 12.14.0 (the newest past the 7-day age gate); the other build and test tooling is current.
+
 ## 2026-10-21 - 33.17.0
 
 ### Features

package/dist_catalog/catalog.digest

@@ -1 +1 @@
-sha256:fa1d470672b5b5d56b05dcf1f16ab395329a8b298e61f0d137e15a07c63d9a07
+sha256:f32ef786a1a2aa49f5d88660313b6b3d0c554fab253e0f42a6fb3d819e90b6a7