@equinor/fusion-framework-cli 11.1.3 → 11.2.0

package/CHANGELOG.md

@@ -1,5 +1,48 @@
 # Change Log
 
+## 11.2.0
+
+### Minor Changes
+
+- [#3362](https://github.com/equinor/fusion-framework/pull/3362) [`6151ff4`](https://github.com/equinor/fusion-framework/commit/6151ff429fc5dc221a4cb43f11362cf39c2a3136) Thanks [@odinr](https://github.com/odinr)! - Added comprehensive dev-server documentation with architecture overview and configuration guide.
+
+  - Added new `docs/dev-server.md` with complete dev-server documentation
+  - Updated README.md to include dev-server documentation link
+  - Covers dev-server features, architecture, configuration, and troubleshooting
+
+### Patch Changes
+
+- [#3345](https://github.com/equinor/fusion-framework/pull/3345) [`0b53fa8`](https://github.com/equinor/fusion-framework/commit/0b53fa8dcd31b0b333a172bfcc15b342c5548bf9) Thanks [@odinr](https://github.com/odinr)! - Documented missing breaking change for Vite configuration file naming in CLI v11 migration guide and changelog.
+
+  - Added detailed explanation of `app.vite.config.ts` → `vite.config.ts` file naming change
+  - Emphasized that `vite.config.ts` should be a last resort for custom setups
+  - Recommended using `dev-server.config.js` instead to avoid unexpected behavior
+  - Updated migration checklist to include the file rename requirement
+  - Enhanced v11.0.0 changelog with the breaking change documentation
+
+  This addresses the undocumented breaking change that could cause time-consuming debugging for developers upgrading from v10 to v11.
+
+- Updated dependencies [[`1f629b5`](https://github.com/equinor/fusion-framework/commit/1f629b556c4e26170b1eb6ad8823c082cb2ac59d)]:
+  - @equinor/fusion-framework-module-msal-node@1.0.3
+
+## 11.1.4
+
+### Patch Changes
+
+- [#3356](https://github.com/equinor/fusion-framework/pull/3356) [`2e47652`](https://github.com/equinor/fusion-framework/commit/2e47652aba8ab14dea62307953666d8f136d7ca0) Thanks [@odinr](https://github.com/odinr)! - Fix SemVer 2.0 compliance issue where build metadata was stripped from package versions.
+
+  - Disabled built-in normalization in `read-package-up` to preserve version build metadata
+  - Added manual package data normalization using `normalize-package-data` library
+  - Preserves original version with build metadata (e.g., `11.8.0+commit`) in app manifests
+  - Maintains backward compatibility with existing version formats
+  - Resolves issue where `+` build metadata was being stripped from versions in `app-manifest.json`
+
+  This fix enables proper SemVer 2.0 compliant versioning for applications built with the CLI.
+
+  Fixes https://github.com/equinor/fusion/issues/657
+
+  Thanks to [@v3gard](https://github.com/v3gard) for identifying and reporting this SemVer compliance issue.
+
 ## 11.1.3
 
 ### Patch Changes
@@ -195,6 +238,7 @@
   - **Dev Portal Modularization:** The dev portal has been moved to a separate package `@equinor/fusion-framework-dev-server`, enabling modular architecture and independent updates. The dev portal can be configured via `dev-server.config.js` and supports live preview and API mocking.
   - **Command Structure:** CLI is now divided into three main groups: `bin` (executable functions), `commands` (CLI commands), and `lib` (for consumers, config, and utilities). This improves organization and modularity.
   - **BREAKING:** The `--service` flag has been removed. The CLI now uses service discovery via Fusion environment variables. All `app -build-???` commands are deprecated and will be removed in the next major version.
+  - **BREAKING:** Vite configuration file naming has changed to follow Vite's standard convention. Rename `app.vite.config.ts` to `vite.config.ts` to ensure your Vite configurations are applied correctly. Note: Using `vite.config.ts` should be a last resort for custom setups - prefer dev-server configuration to avoid unexpected behavior.
 
   - **Dev Server Abstraction:** Vite configuration and dev server functionality has been abstracted into the `@equinor/fusion-framework-dev-server` package. The CLI now provides a higher-level API that handles Vite configuration internally, eliminating the need for users to manage Vite configuration directly while still allowing for customization through configuration options.
 

package/README.md

@@ -122,6 +122,7 @@ A minimal example for a Fusion Framework app:
 **Getting Started**
 - [Developing Apps](docs/application.md): Complete guide to building, configuring, and deploying Fusion applications
 - [Developing Portals](docs/portal.md): Guide to building, configuring, and publishing portal templates
+- [Dev Server](docs/dev-server.md): Understanding how the development server works, including architecture and configuration
 
 **Setup & Configuration**
 - [Authentication](docs/auth.md): Setting up authentication for local development and CI/CD environments