@equinor/fusion-framework-cli 13.2.0 → 13.2.1

package/dist/esm/version.js

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

package/dist/types/version.d.ts

@@ -1 +1 @@
-export declare const version = "13.2.0";
+export declare const version = "13.2.1";

package/docs/application.md

@@ -424,7 +424,7 @@ This command uploads and tags your app for deployment. If no bundle is provided,
 | `[bundle]`         | Path to the app bundle to upload. If omitted, the CLI will build and bundle your app automatically. When provided, app validation uses metadata from the bundle instead of local files. |                   |
 | `-e`, `--env`      | Target environment for deployment (e.g., `ci`, `fqa`, `fprd`).                                      |                   |
 | `-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 (`latest` \| `preview`).                                          | `latest`          |
+| `-t`, `--tag`      | Tag to apply to the published app (any string, commonly `latest` or `preview`).                    | `latest`          |
 | `-d`, `--debug`    | Enable debug mode for verbose logging.                                                              | `false`           |
 | `--token`          | Authentication token for Fusion.                                                                    |                   |
 | `--tenantId`       | Azure tenant ID for authentication.                                                                 |                   |
@@ -449,7 +449,7 @@ pnpm fusion-framework-cli publish --tag latest app-bundle.zip
 >
 > **Additional Notes**:
 > - **Artifact-based publishing**: When providing a bundle, the command extracts app metadata from `metadata.json` within the bundle, enabling publishing from any directory without requiring local project files.
-> - The `--tag` option lets you mark the published version (e.g., as `latest` or `preview`) for easier deployment targeting.
+> - The `--tag` option lets you mark the published version with any custom tag (e.g., `latest`, `preview`, `dev`, `staging`, `v1.0`) for easier deployment targeting.
 > - 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.
 
@@ -591,11 +591,11 @@ Tag a published application version in the Fusion app store (registry).
 
 Tag a specific version of your Fusion application in the Fusion app registry for release management.
 
-The `tag` command applies a tag (such as `latest`, `preview`, or `stable`) to a published application version. This helps you manage which version is considered the default for deployment or preview purposes.
+The `tag` command applies a tag (such as `latest`, `preview`, `dev`, `staging`, or any custom string) to a published application version. This helps you manage which version is considered the default for deployment or preview purposes.
 
 | Argument/Option           | Description                                                        | Default / Example |
 | ------------------------- | ------------------------------------------------------------------ | ----------------- |
-| `<tag>`                   | Tag to apply (`latest` \| `preview` \| `stable`).                  |                   |
+| `<tag>`                   | Tag to apply (any string, e.g., `latest`, `preview`, `dev`, `staging`).     |                   |
 | `-p, --package`           | Package to tag in format name@version.                              |                   |
 | `-m, --manifest <string>` | Manifest file to use for resolving app key and version.            | `app.manifest.ts` |
 | `--debug`                 | Enable debug mode for verbose logging.                             | `false`           |
@@ -621,7 +621,7 @@ pnpm fusion-framework-cli app tag latest --package my-app@1.2.3
 
 > [!NOTE]
 > - The `tag` command requires a published application version. You can specify the package name and version using `--package`, or let the CLI resolve them from your manifest file.
-> - Supported tags are: `latest` and `preview`.
+> - Tags can be any string value. Common examples include `latest`, `preview`, `dev`, `staging`, or version numbers like `v1.0`.
 > - Authentication options (`--token`, `--tenantId`, `--clientId`) can be set via CLI flags or environment variables.
 > - If tagging fails, an error will be logged and the process will exit with a non-zero code.
 

package/docs/portal.md

@@ -159,7 +159,7 @@ pnpm fusion-framework-cli portal publish --tag preview --schema portal.schema.ts
 > **Building Behavior**: Unlike the app publish command—which only builds your app if a pre-built bundle is not provided—the portal publish command always builds your portal template before uploading and tagging. There is no option to provide a pre-built bundle.
 > 
 > **Additional Notes**:
-> - The `--tag` option lets you mark the published version (e.g., as `latest` or `preview`) for easier deployment targeting.
+> - The `--tag` option lets you mark the published version with any custom tag (e.g., `latest`, `preview`, `dev`, `staging`) for easier deployment targeting.
 > - 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.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@equinor/fusion-framework-cli",
-  "version": "13.2.0",
+  "version": "13.2.1",
   "keywords": [
     "Fusion",
     "Fusion Framework",
@@ -112,8 +112,8 @@
     "zod": "^4.1.8",
     "@equinor/fusion-framework-dev-portal": "1.4.0",
     "@equinor/fusion-framework-dev-server": "1.1.21",
-    "@equinor/fusion-framework-module-msal-node": "3.0.0",
-    "@equinor/fusion-imports": "1.1.10"
+    "@equinor/fusion-imports": "1.1.10",
+    "@equinor/fusion-framework-module-msal-node": "3.0.0"
   },
   "devDependencies": {
     "@rollup/plugin-commonjs": "^29.0.0",
@@ -139,12 +139,12 @@
     "vitest": "^3.2.4",
     "@equinor/fusion-framework-cli-plugin-ai-chat": "1.0.4",
     "@equinor/fusion-framework-cli-plugin-ai-index": "1.0.4",
+    "@equinor/fusion-framework-cli-plugin-ai-mcp": "1.0.4",
     "@equinor/fusion-framework-cli-plugin-ai-search": "1.0.4",
     "@equinor/fusion-framework-module": "5.0.5",
-    "@equinor/fusion-framework-cli-plugin-ai-mcp": "1.0.4",
-    "@equinor/fusion-framework-module-service-discovery": "9.0.5",
+    "@equinor/fusion-framework-module-app": "7.4.0",
     "@equinor/fusion-framework-module-http": "7.0.6",
-    "@equinor/fusion-framework-module-app": "7.3.0"
+    "@equinor/fusion-framework-module-service-discovery": "9.0.5"
   },
   "peerDependenciesMeta": {
     "typescript": {