@serve.zone/appstore 32.24.0 → 32.26.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/apps/cloudly/app.json +2 -2
- package/apps/cloudly/versions/1.25.0/config.json +173 -0
- package/apps/cloudly/versions/1.26.0/config.json +173 -0
- package/appstore.json +1 -1
- package/changelog.md +25 -0
- package/dist_ts_client/data.generated.js +352 -4
- package/package.json +1 -1
- package/readme.md +2 -2
- package/ts_client/data.generated.ts +351 -3
package/changelog.md
CHANGED
|
@@ -1,5 +1,30 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 2026-10-07 - 32.26.0
|
|
4
|
+
|
|
5
|
+
### Features
|
|
6
|
+
|
|
7
|
+
- publish the Cloudly 1.26.0 template for Cloudly 33.17.1 (cloudly)
|
|
8
|
+
- Add Cloudly app version 1.26.0, pinned to the Cloudly 33.17.1 multi-platform image index `code.foss.global/serve.zone/cloudly@sha256:41ec10edac38281acd084c1e034bbd090a0f684a31d467b25c8787ab73d75fc5` (tag `v33.17.1`), and mark it as the latest catalog version.
|
|
9
|
+
- Cloudly 33.17.0, which 1.25.0 pins, crash-looped at its first start on a database holding Pallet-era nodes: its first data step `cluster-node-hostname-intent` (0.25.0 → 0.26.0) stated each intent through the node and cluster models, which startup has not prepared while it runs the data steps, and was refused before its first write. Cloudly 33.17.1 runs that step on the stored documents directly, like the other data steps. The migration ledger does not advance past a failed step, so an install on 1.25.0 whose first start failed stayed at data version 0.25.0 and upgrades to 1.26.0 normally.
|
|
10
|
+
- Keep the 1.25.0 runtime contract and upgrade flags: 1.26.0 differs from 1.25.0 only in its image and changelog. Cloudly 33.17.1 changes neither `qenv.yml` nor the Dockerfile, and the Onebox minimum stays 33.8.0. It keeps the data steps of 33.17.0 from 0.25.0 to 0.28.0 (`cluster-node-hostname-intent`, `deployment-operation-route-evidence`, `service-secret-target-predecessor`), and every Cloudly before 33.17.0 refuses the migrated data; the template stays breaking, migration-required, backup-before-upgrade and manual-review.
|
|
11
|
+
- The template changelog states the failure and the fix, and carries the 1.25.0 text as the changes of Cloudly 33.17.0 that apply from 1.24.0 or earlier; the carried rollout order now names Cloudly 33.17.1, and the upgrade flags statement names an upgrade from a 1.25.0 whose first start failed.
|
|
12
|
+
- Update the bundled client data, the README guidance and the resolver regression coverage, which now holds 1.25.0 to 1.26.0 apart from the image and changelog.
|
|
13
|
+
|
|
14
|
+
## 2026-10-07 - 32.25.0
|
|
15
|
+
|
|
16
|
+
### Features
|
|
17
|
+
|
|
18
|
+
- publish the Cloudly 1.25.0 template for Cloudly 33.17.0 (cloudly)
|
|
19
|
+
- Add Cloudly app version 1.25.0, pinned to the Cloudly 33.17.0 multi-platform image index `code.foss.global/serve.zone/cloudly@sha256:177269c8044604f70c0a5c045479b36222876685a2b8bde70ee76e43e4568ab7` (tag `v33.17.0`), and mark it as the latest catalog version.
|
|
20
|
+
- Keep the 1.24.0 runtime contract and upgrade flags: 1.25.0 differs from 1.24.0 only in its image and changelog. Cloudly 33.17.0 changes neither `qenv.yml` nor the Dockerfile, and the Onebox minimum stays 33.8.0. It moves the data version from 0.25.0 to 0.28.0 through the forward-only steps `cluster-node-hostname-intent` (0.26.0), `deployment-operation-route-evidence` (0.27.0) and `service-secret-target-predecessor` (0.28.0), so every upgrade runs a data step and every Cloudly before 33.17.0 refuses the migrated data; the template stays breaking, migration-required, backup-before-upgrade and manual-review.
|
|
21
|
+
- The template changelog names what 33.17.0 changes for an operator: a legacy import takes over its legacy service's route claims and can reserve, where Cloudly 33.16.0 refused every `tsdeploy import-legacy` reserve `ROUTE_UNAVAILABLE`; Cloudly owns a node's hostname (`setClusterNodeHostname`, `resetClusterNodeHostname`, interfaces 32.52.0, `cloudly-worker-<name>` by default) and routes a Pallet service by node id, so a rename moves no traffic; a routeless deployment records its empty route evidence when it succeeds; a cluster's designated ingress service cannot be deleted while designated, and a designation whose bearer is no longer active is recovered; a deleted service's secret target state goes with its row. The data-step statements carried from earlier versions now name the 0.25.0 to 0.28.0 steps.
|
|
22
|
+
- Update the bundled client data, the README guidance and the resolver regression coverage, which now holds 1.24.0 to 1.25.0 apart from the image and changelog.
|
|
23
|
+
|
|
24
|
+
### Maintenance
|
|
25
|
+
|
|
26
|
+
- Release tooling: pnpm 12.8.1 → 12.8.2. `@types/node` stays at 26.6.3 until 26.6.4 is seven days old (2026-10-08 22:39 UTC); the `@git.zone` tools are current.
|
|
27
|
+
|
|
3
28
|
## 2026-10-07 - 32.24.0
|
|
4
29
|
|
|
5
30
|
### Features
|