@serve.zone/appstore 33.4.0 → 33.6.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/changelog.md +31 -0
- package/dist_catalog/catalog.digest +1 -1
- package/dist_catalog/catalog.envelope.json +561 -6
- package/dist_catalog/catalog.json +559 -4
- package/dist_ts_client/storage.d.ts +3 -2
- package/dist_ts_client/storage.js +19 -5
- package/dist_ts_client/types.d.ts +11 -0
- package/package.json +2 -2
- package/readme.md +30 -4
- package/ts_client/readme.md +1 -1
- package/ts_client/storage.ts +22 -4
- package/ts_client/types.ts +15 -0
package/changelog.md
CHANGED
|
@@ -1,5 +1,36 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 2026-10-13 - 33.6.0
|
|
4
|
+
|
|
5
|
+
### Features
|
|
6
|
+
|
|
7
|
+
- normalize App Store backup exclusions into the storage handoff (storage)
|
|
8
|
+
- `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.
|
|
9
|
+
- 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.
|
|
10
|
+
- publish Cloudly templates 1.28.5 and 1.28.6, which declare Cloudly's workload logs non-backup data (cloudly)
|
|
11
|
+
- 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).
|
|
12
|
+
- 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.
|
|
13
|
+
- 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.
|
|
14
|
+
- 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.
|
|
15
|
+
|
|
16
|
+
### Maintenance
|
|
17
|
+
|
|
18
|
+
- release tooling: pnpm 12.10.1
|
|
19
|
+
|
|
20
|
+
## 2026-10-13 - 33.5.0
|
|
21
|
+
|
|
22
|
+
### Features
|
|
23
|
+
|
|
24
|
+
- publish the Cloudly 1.28.4 template for Cloudly 33.19.2 (cloudly)
|
|
25
|
+
- Add Cloudly app version 1.28.4, pinned to the Cloudly 33.19.2 multi-platform image index `code.foss.global/serve.zone/cloudly@sha256:0dd5399877c894b86f55d7a56df2da597bfcb7d1c8ec8adec547bfebb5d091d9` (tag `v33.19.2`), record it in `catalog.lock.json`, qualify it in `test/test.cloudlytemplates.node.ts` and mark it as Cloudly's latest version.
|
|
26
|
+
- Cloudly 33.19.2 is a fixes-only patch over 33.19.1: a greenfield deployment, a legacy import's successor included, proves its namespace blank on the nodes of the Pallet clusters only, so a fleet that still keeps a Coreflow-owned Swarm cluster without a relay can reserve one; a greenfield rollout without a Pallet runtime spec is refused `GREENFIELD_PALLET_RUNTIME_SPEC_REQUIRED` instead of falling back to Coreflow placement; and a node's network compilation proves each workload lease and each authority or eligibility proof once per transaction (100 endpoints: 539 reads instead of 2,839).
|
|
27
|
+
- Keep the 1.28.3 runtime contract: 1.28.4 differs from 1.28.3 only in its image and changelog. Cloudly 33.19.2 adds no data step and no collection, keeps the data version 0.30.0 and changes neither the Dockerfile nor a `qenv.yml` requirement, and the Onebox minimum stays 33.8.0. The template stays breaking, migration-required, backup-before-upgrade and manual-review.
|
|
28
|
+
- The 1.28.4 changelog carries its own changes, those of 33.18.3 to 33.19.1 (1.28.3's, with its EFENCE_BUSY start note for an upgrade from 1.28.2 or earlier), the Pallet 36.3.0 prerequisite of 33.18.2 and the upgrade path from every earlier template, and names cloudly@1.28.2 for the rest.
|
|
29
|
+
|
|
30
|
+
### Maintenance
|
|
31
|
+
|
|
32
|
+
- Release tooling: pnpm 12.9.1 → 12.10.0 (`packageManager`, `pnpm-lock.yaml`; the newest pnpm 12 at least seven days old on 2026-10-13 before 17:36 UTC: 12.10.1 and 12.11.x are younger). `@types/node` stays 26.6.4 (26.6.5 is four days old); `@git.zone/tsbuild` 6.0.2, `@git.zone/tsdoc` 3.0.2 and `@git.zone/tstest` 7.2.1 are current.
|
|
33
|
+
|
|
3
34
|
## 2026-10-13 - 33.4.0
|
|
4
35
|
|
|
5
36
|
### Features
|
|
@@ -1 +1 @@
|
|
|
1
|
-
sha256:
|
|
1
|
+
sha256:e86081be018dd1c01c4153c13493f4de9d00ea28abd9b8dddf67cfa4afd63880
|