@serve.zone/appstore 33.5.0 → 33.7.0

package/changelog.md

@@ -1,5 +1,32 @@
 # Changelog
 
+## 2026-10-14 - 33.7.0
+
+### Features
+
+- publish the Cloudly 1.29.0 template for Cloudly 33.20.0 (cloudly)
+  - Add Cloudly app version 1.29.0, pinned to the Cloudly 33.20.0 multi-platform image index `code.foss.global/serve.zone/cloudly@sha256:0fa3b6a1fcf0d003c2e7397fbc774dbc35815d5c75492b4ec12f2474961f683e` (tag `v33.20.0`), record it in `catalog.lock.json`, qualify it in `test/test.cloudlytemplates.node.ts` and make it Cloudly's latest version.
+  - Keep the 1.28.6 runtime contract: 1.29.0 differs from 1.28.6 only in its image and changelog, so it keeps `backupExclusions` for `runtime-logs/` and `requiresFeatures: ['storage.object-storage.backup-exclusions']` (owner decision 2026-10-13: workload logs are not part of backups) and is the upgrade target of 1.28.6 and 1.28.5; a host without the feature lists it and refuses it, and its newest Cloudly target stays 1.28.4. Cloudly's `ts_migration` is unchanged from `v33.19.2` to `v33.20.0`: no data step, data version 0.30.0, no Dockerfile or `qenv.yml` change, Onebox minimum 33.8.0.
+  - Keep breaking, manual-review, migration-required and backup-before-upgrade: hosts read the flags from the target version alone, every upgrade from 1.26.0 or earlier runs the forward-only 0.28.0 to 0.30.0 steps, and Cloudly 33.19.2 and earlier refuse the workload log ledger rows 33.20.0 writes (their exact row assertion has no `payload` member), so a return to an earlier template needs the backup taken before the upgrade.
+  - The 1.29.0 changelog carries the changes of 33.20.0 (non-public hostnames served to dcrouter through `dcrouterForwardSourceAddresses`, workload logs as segments with the new collection `cloudly_runtime_log_inline_payloads` and its `EFENCE_BUSY` first-start note, redeploy over an unexecutable retained plan), the backup-exclusions declaration and the upgrade path from 1.28.6 and 1.28.5, then the 1.28.4 changelog for Cloudly 33.19.2 and every earlier template.
+
+## 2026-10-13 - 33.6.0
+
+### Features
+
+- normalize App Store backup exclusions into the storage handoff (storage)
+  - `normalizeAppStoreStorageConfig` returns `backupExclusions`, the key prefixes and reason a version's `backupExclusions` (`@serve.zone/interfaces` 32.56.0) declares, by object-storage request id: `legacy-s3` for `platformRequirements.s3`, empty when the version declares none (`TAppStoreNormalizedBackupExclusion`). A backup leaves those objects out; a restore neither brings them back nor removes them.
+  - A declared exclusion adds `storage.object-storage.backup-exclusions` to `requiredFeatureIds` and fails closed like an explicit request when the target does not advertise it. The interfaces contract judges every exclusion before normalization.
+- publish Cloudly templates 1.28.5 and 1.28.6, which declare Cloudly's workload logs non-backup data (cloudly)
+  - Owner decision 2026-10-13: workload logs are not part of Cloudly's backups; a restore brings back state, not past logs. Both templates declare `backupExclusions: [{ storageRequest: 'legacy-s3', keyPrefixes: ['runtime-logs/'], reason: 'Workload logs; a restore brings back state, not past logs.' }]`, the prefix under which Cloudly keeps its workload log payloads, and `requiresFeatures: ['storage.object-storage.backup-exclusions']`, so a host that does not fulfil the feature keeps listing them and refuses them as targets (its newest Cloudly target stays 1.28.4).
+  - 1.28.5 is 1.28.3 (Cloudly 33.19.1, image index `sha256:ff692cf950da26d1d50e717c06eff1c58201b699e6bb94d65a541cd861abbedc`) with the declaration, so a host on 1.28.3 moves its template without moving Cloudly. It sorts above 1.28.4 but runs the older image; its changelog says so and sends a host on 1.28.4 to 1.28.6.
+  - 1.28.6 is 1.28.4 (Cloudly 33.19.2, image index `sha256:0dd5399877c894b86f55d7a56df2da597bfcb7d1c8ec8adec547bfebb5d091d9`) with the declaration and is Cloudly's latest version. Both keep the upgrade flags and the Onebox 33.8.0 minimum of their source; their changelogs state the declaration and the upgrade path, then repeat the source's.
+  - Record both in `catalog.lock.json`; `test/test.cloudlytemplates.node.ts` qualifies that a template moving only its declarations differs from its source in them and its changelog alone, and `test/test.succession.node.ts` that the catalog only adds to the one published before and that a consumer without the feature activates it and keeps 1.28.4 as its target.
+
+### Maintenance
+
+- release tooling: pnpm 12.10.1
+
 ## 2026-10-13 - 33.5.0
 
 ### Features

package/dist_catalog/catalog.digest

@@ -1 +1 @@
-sha256:9d32dca22c9b52e3536020e43ad845d95978c7e663cb5d5c61edacb918f0d815
+sha256:747ea478ea4c79aacc22e70a7c9a2568101fb78f8f50373dfbd5fee57fb63c16