@serve.zone/interfaces 17.2.0 → 17.3.0

package/changelog.md

@@ -1,5 +1,19 @@
 # Changelog
 
+## 2026-07-23 - 17.3.0
+
+### Features
+
+- add service image retention count option (data-service)
+  - Adds optional imageRetentionCount to service data definitions for configuring pushed image version retention.
+  - Documents the platform default retention count of 3 and protection for active desired or immutable deployments.
+
+## 2026-07-22 - 17.2.1
+
+### Fixes
+
+- persist exact original placement and target confirmation in service migration contracts
+
 ## 2026-07-22 - 17.2.0
 
 ### Features

package/dist_ts/00_commitinfo_data.js

@@ -3,7 +3,7 @@
  */
 export const commitinfo = {
     name: '@serve.zone/interfaces',
-    version: '17.2.0',
+    version: '17.3.0',
     description: 'Shared TypeScript interfaces and TypedRequest contracts for the serve.zone ecosystem.'
 };
 //# sourceMappingURL=data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoiMDBfY29tbWl0aW5mb19kYXRhLmpzIiwic291cmNlUm9vdCI6IiIsInNvdXJjZXMiOlsiLi4vdHMvMDBfY29tbWl0aW5mb19kYXRhLnRzIl0sIm5hbWVzIjpbXSwibWFwcGluZ3MiOiJBQUFBOztHQUVHO0FBQ0gsTUFBTSxDQUFDLE1BQU0sVUFBVSxHQUFHO0lBQ3hCLElBQUksRUFBRSx3QkFBd0I7SUFDOUIsT0FBTyxFQUFFLFFBQVE7SUFDakIsV0FBVyxFQUFFLHVGQUF1RjtDQUNyRyxDQUFBIn0=

package/dist_ts/data/migration.d.ts

@@ -1,3 +1,4 @@
+import type { IServicePlacement } from './service.js';
 export type TServiceMigrationStatus = 'running' | 'completed' | 'failed';
 export type TServiceMigrationStepStatus = 'pending' | 'running' | 'completed' | 'failed' | 'skipped';
 export type TServiceMigrationStepKey = 'validate' | 'stop-source' | 'snapshot' | 'restore' | 'deploy-target' | 'verify';
@@ -13,7 +14,9 @@ export interface IServiceMigrationStep {
  * A node-to-node service migration orchestrated by Cloudly:
  * gracefully stop everywhere -> snapshot data on the source ->
  * restore on the target -> deploy pinned to the target -> verify.
- * On failure before deploy, placement rolls back to the source.
+ * Until the target deployment is confirmed, failure rollback restores the
+ * exact original placement snapshot. Target confirmation is the durable
+ * commit point; after it, rollback must not reactivate the source placement.
  */
 export interface IServiceMigration {
     id: string;
@@ -23,6 +26,22 @@ export interface IServiceMigration {
     targetNodeName: string;
     /** Backup archive id used for the data move (migration-<id>). */
     backupId?: string;
+    /**
+     * Exact placement captured before the migration mutates desired state.
+     * A non-null value is restored verbatim during pre-commit rollback. `null`
+     * means the service originally had no placement property, so rollback must
+     * remove that property. `undefined` is reserved for legacy records whose
+     * original placement is unknown and must not be interpreted as absent.
+     */
+    originalPlacement?: IServicePlacement | null;
+    /**
+     * Timestamp at which the target deployment was positively verified and the
+     * migration crossed its durable commit point. While `null` or absent, a
+     * failure is pre-commit and restores `originalPlacement`; once set, failure
+     * handling must keep the target authoritative and must not restore source
+     * placement.
+     */
+    targetDeploymentConfirmedAt?: number | null;
     status: TServiceMigrationStatus;
     steps: IServiceMigrationStep[];
     startedAt: number;

package/dist_ts/data/service.d.ts

@@ -148,6 +148,13 @@ export interface IService {
          * For example, 3 for cores3 or coremongo
          */
         maxReplicas?: number;
+        /**
+         * How many pushed image versions to keep for this service. Older
+         * versions beyond this count are pruned from the registry, always
+         * protecting versions referenced by the current desired state or an
+         * active immutable deployment. Absent means the platform default of 3.
+         */
+        imageRetentionCount?: number;
         /**
          * Whether to enforce anti-affinity rules
          * When true, tries to spread deployments across different BareMetal servers

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@serve.zone/interfaces",
-  "version": "17.2.0",
+  "version": "17.3.0",
   "private": false,
   "description": "Shared TypeScript interfaces and TypedRequest contracts for the serve.zone ecosystem.",
   "exports": {

package/ts/00_commitinfo_data.ts

@@ -3,6 +3,6 @@
  */
 export const commitinfo = {
   name: '@serve.zone/interfaces',
-  version: '17.2.0',
+  version: '17.3.0',
   description: 'Shared TypeScript interfaces and TypedRequest contracts for the serve.zone ecosystem.'
 }

package/ts/data/migration.ts

@@ -1,3 +1,5 @@
+import type { IServicePlacement } from './service.js';
+
 export type TServiceMigrationStatus = 'running' | 'completed' | 'failed';
 
 export type TServiceMigrationStepStatus = 'pending' | 'running' | 'completed' | 'failed' | 'skipped';
@@ -23,7 +25,9 @@ export interface IServiceMigrationStep {
  * A node-to-node service migration orchestrated by Cloudly:
  * gracefully stop everywhere -> snapshot data on the source ->
  * restore on the target -> deploy pinned to the target -> verify.
- * On failure before deploy, placement rolls back to the source.
+ * Until the target deployment is confirmed, failure rollback restores the
+ * exact original placement snapshot. Target confirmation is the durable
+ * commit point; after it, rollback must not reactivate the source placement.
  */
 export interface IServiceMigration {
   id: string;
@@ -33,6 +37,22 @@ export interface IServiceMigration {
   targetNodeName: string;
   /** Backup archive id used for the data move (migration-<id>). */
   backupId?: string;
+  /**
+   * Exact placement captured before the migration mutates desired state.
+   * A non-null value is restored verbatim during pre-commit rollback. `null`
+   * means the service originally had no placement property, so rollback must
+   * remove that property. `undefined` is reserved for legacy records whose
+   * original placement is unknown and must not be interpreted as absent.
+   */
+  originalPlacement?: IServicePlacement | null;
+  /**
+   * Timestamp at which the target deployment was positively verified and the
+   * migration crossed its durable commit point. While `null` or absent, a
+   * failure is pre-commit and restores `originalPlacement`; once set, failure
+   * handling must keep the target authoritative and must not restore source
+   * placement.
+   */
+  targetDeploymentConfirmedAt?: number | null;
   status: TServiceMigrationStatus;
   steps: IServiceMigrationStep[];
   startedAt: number;

package/ts/data/service.ts

@@ -291,6 +291,14 @@ export interface IService {
      * For example, 3 for cores3 or coremongo
      */
     maxReplicas?: number;
+
+    /**
+     * How many pushed image versions to keep for this service. Older
+     * versions beyond this count are pruned from the registry, always
+     * protecting versions referenced by the current desired state or an
+     * active immutable deployment. Absent means the platform default of 3.
+     */
+    imageRetentionCount?: number;
     
     /**
      * Whether to enforce anti-affinity rules