@equinor/fusion-framework-cli 15.6.2 → 15.7.0

package/dist/esm/version.js

@@ -1,3 +1,3 @@
 // Generated by genversion.
-export const version = '15.6.2';
+export const version = '15.7.0';
 //# sourceMappingURL=version.js.map

package/dist/types/bin/upload-application.d.ts

@@ -12,6 +12,7 @@ import { type ConsoleLogger } from './utils/index.js';
  * @property appKey - Optional application key to override bundle metadata.
  * @property framework - The FusionFramework instance used for service discovery and requests.
  * @property log - Optional logger for outputting progress and debug information.
+ * @property allowExistingVersion - Reuse the exact bundle version only on a structured duplicate-version upload conflict.
  *
  * @public
  */
@@ -20,6 +21,7 @@ type UploadApplicationOptions = {
     appKey?: string;
     framework: FusionFramework;
     log?: ConsoleLogger;
+    allowExistingVersion?: boolean;
 };
 /**
  * Uploads an application bundle to the app service for publishing or updating an app.
@@ -29,12 +31,13 @@ type UploadApplicationOptions = {
  * for common failure scenarios, including HTTP status codes and bundle reading issues.
  *
  * @param opt - Options for bundle file, app key, framework, and logger.
- * @returns The response from the app service, or an empty object if the response cannot be parsed.
+ * @returns The uploaded app identity, or the bundle identity marked `existingVersion` on an opted-in duplicate response. Existing versions must still be tagged by the caller.
  * @throws If bundle reading or upload fails, or if the app service returns an error status.
  * @public
  */
 export declare const uploadApplication: (opt: UploadApplicationOptions) => Promise<{
     appKey: string;
     version: string;
+    existingVersion?: true;
 }>;
 export default uploadApplication;

package/dist/types/bin/upload-application.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/types/cli/commands/app/publish.command.d.ts

@@ -9,6 +9,7 @@
  * - Supports specifying environment, manifest file, and tag.
  * - Debug mode and authentication options are supported.
  * - Supports `--snapshot` flag to publish with a snapshot version without modifying package.json.
+ * - Supports `--allow-existing-version` to re-tag an exact existing bundle version on a duplicate upload response.
  *
  * Usage:
  *   $ ffc app publish [bundle] [options]

package/dist/types/cli/commands/app/publish.command.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/types/version.d.ts

@@ -1 +1 @@
-export declare const version = "15.6.2";
+export declare const version = "15.7.0";

package/docs/application.md

@@ -497,6 +497,7 @@ This command uploads and tags your app for deployment. If no bundle is provided,
 | `-m`, `--manifest` | Manifest file to use for bundling (e.g., `app.manifest.ts`) (optional).                             | `app.manifest.ts` |
 | `-t`, `--tag`      | Tag to apply to the published app (any string, commonly `latest` or `preview`).                    | `latest`          |
 | `-c`, `--config`   | Upload application config after publishing. Accepts true for default config file or a path to a specific config file. |                   |
+| `--allow-existing-version` | On a confirmed duplicate-version upload response, re-tag the exact existing bundle version instead of failing. | `false` |
 | `-d`, `--debug`    | Enable debug mode for verbose logging.                                                              | `false`           |
 | `--token`          | Authentication token for Fusion.                                                                    |                   |
 | `--tenantId`       | Azure tenant ID for authentication.                                                                 |                   |
@@ -529,6 +530,49 @@ pnpm fusion-framework-cli publish --config app.config.prod.ts --env prod
 > - Authentication options (`--token`, `--tenantId`, `--clientId`) can be set via CLI flags or environment variables.
 > - If any step fails (build, upload, or tagging), an error will be logged and the process will exit with a non-zero code.
 
+#### Re-deploy an existing version
+
+Use `ffc app publish --allow-existing-version` to re-run a deployment or move a tag
+back to an older published bundle without generating another version:
+
+```sh
+# Restore latest to the exact version in a previously published artifact.
+ffc app publish --env ci --tag latest --allow-existing-version previous.bundle.zip
+
+# Restore a pull-request preview tag.
+ffc app publish --env ci --tag pr-42 --allow-existing-version app.bundle.zip
+```
+
+The option is disabled by default. Omit it to retain duplicate-version failures.
+An ordinary successful upload is unchanged when the option is enabled.
+
+Recovery requires an HTTP **409 from bundle upload** whose JSON `error` has
+`code: "ConflictError"`, `resourceIdentifier: "version"`, and
+`message: "An app build with version <version> already exists"`. The version must
+exactly match the lowercased, valid semantic version in the uploaded ZIP's
+`app-manifest.json`. The app key is the same key used for that upload, resolved
+from the bundle metadata or an explicit programmatic override. The CLI does not
+guess from the working directory, a tag, `package.json`, or a log message.
+Unknown, malformed or mismatched responses still fail.
+
+On that specific response, the CLI does not retry the upload. It tags the existing
+version with the original `--tag`, using the same initialized framework,
+authentication and `--env`. If requested, `--config` generation and publication
+still run for that version. Only after tagging and requested config publication
+succeed does the CLI report that the existing version was re-tagged.
+
+Authentication, discovery, network, validation, unrelated conflicts, tagging and
+config failures remain failures. A config failure can occur after the tag has
+already moved; publishing is not transactional. Reusing a version deploys the
+**existing** registry contents, not the newly supplied ZIP contents, and does not
+compare their bytes. Use a new version when the build contents have changed.
+
+For programmatic callers, `uploadApplication({ ..., allowExistingVersion: true })`
+returns `{ appKey, version, existingVersion: true }` only for the confirmed
+duplicate response. This result is not a completed deployment: the caller must
+still tag that version and complete any requested config publication. Successful
+new uploads retain the existing `{ appKey, version }` result shape.
+
 ### Config
 
 Upload your application configuration to the Fusion app store (registry).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@equinor/fusion-framework-cli",
-  "version": "15.6.2",
+  "version": "15.7.0",
   "keywords": [
     "Fusion",
     "Fusion Framework",
@@ -94,11 +94,11 @@
     "directory": "packages/cli"
   },
   "dependencies": {
-    "@equinor/fusion-framework-dev-portal": "11.1.7",
+    "@equinor/fusion-framework-dev-portal": "11.1.8",
     "@equinor/fusion-framework-dev-server": "2.3.2",
     "@equinor/fusion-framework-module-azure-identity": "0.3.4",
     "@equinor/fusion-framework-vite-plugin-raw-imports": "2.0.5",
-    "@equinor/fusion-framework-vite-plugin-react-router": "0.1.4",
+    "@equinor/fusion-framework-vite-plugin-react-router": "0.1.5",
     "@equinor/fusion-imports": "2.0.7",
     "@types/inquirer": "^9.0.9",
     "chalk": "^6.0.0",