Skip to content

Releases: equinor/fusion-framework

@equinor/[email protected]

30 Jan 09:53
e88d94b

Choose a tag to compare

Patch Changes

  • #3986 5211e98 Thanks @Noggling! - Fix CLI commands outputting invalid JSON due to dotenv messages appearing in stdout. Commands like ffc app manifest now produce clean JSON output suitable for automated tooling and CI/CD pipelines.

  • #3988 69b658a Thanks @asbjornhaland! - Fix CLI app config not passing the potential logger to publishAppConfig.

@equinor/[email protected]

29 Jan 11:46
340aa83

Choose a tag to compare

Minor Changes

  • #3978 54702d7 Thanks @Noggling! - Allow custom string values for app build tags instead of restricting to 'latest' and 'preview'.

    The app module schema now accepts any string value for the tag field in AppBuildManifest and ApiApplicationBuildSchema. This enables using custom deployment tags like dev, staging, v1.0, or any other string value while maintaining backward compatibility with existing latest and preview tags.

    // Before: only 'latest' | 'preview' allowed
    const build: AppBuildManifest = {
      version: "1.0.0",
      entryPoint: "index.js",
      tag: "latest", // or 'preview' only
    };
    
    // After: any string value allowed
    const build: AppBuildManifest = {
      version: "1.0.0",
      entryPoint: "index.js",
      tag: "dev", // or 'staging', 'v1.0', etc.
    };

    This aligns the schema validation with the CLI's existing flexibility for custom tags.

    Fixes: https://github.com/equinor/fusion-core-tasks/issues/252

@equinor/[email protected]

28 Jan 11:40
4912ac0

Choose a tag to compare

Patch Changes

@equinor/[email protected]

28 Jan 11:39
4912ac0

Choose a tag to compare

Major Changes

  • #3929 46a1c71 Thanks @dependabot! - Require Node.js >= 20 for @equinor/fusion-framework-module-msal-node due to upgrading @azure/msal-node and @azure/msal-node-extensions to v5.

    Migration: upgrade runtimes to Node.js 20+.

@equinor/[email protected]

28 Jan 11:39
4912ac0

Choose a tag to compare

Patch Changes

@equinor/[email protected]

28 Jan 11:40
4912ac0

Choose a tag to compare

Minor Changes

  • #3961 343f5f9 Thanks @asbjornhaland! - Add possibility to configure and override service-discovery in AppConfig.

    Allows developers to define overrides in app.config.[ENV].ts:

    export default defineAppConfig(() => ({
      endpoints: {
        admin: {
          url: "MY_OVERRIDDEN_URL", // e.g. an url to a PR-environment
          scopes: [],
        },
      },
    }));

@equinor/[email protected]

28 Jan 11:39
4912ac0

Choose a tag to compare

Patch Changes

  • #3948 62be8e9 Thanks @dependabot! - Internal: update OpenTelemetry dependencies to latest versions (api-logs, exporter-logs-otlp-http, otlp-exporter-base, otlp-transformer, resources, sdk-logs). Includes bug fixes for circular reference handling in logs and improved error retry logic. No public API changes.

  • Updated dependencies [343f5f9, 122752b]:

@equinor/[email protected]

28 Jan 11:40
4912ac0

Choose a tag to compare

Patch Changes

  • #3960 2eb7f69 Thanks @dependabot! - Internal: Updated LangChain dependencies to v1.x (@langchain/community 0.3.59→1.1.8, @langchain/core 1.1.16→1.1.17, langchain 1.2.11→1.2.14) - compatibility update with security fixes

@equinor/[email protected]

28 Jan 11:40
4912ac0

Choose a tag to compare

Patch Changes

@equinor/[email protected]

28 Jan 11:39
4912ac0

Choose a tag to compare

Minor Changes

  • 5121c48 Thanks @Noggling! - Add support for artifact-based app validation in publish command.

    The CLI publish command now supports validating applications using metadata extracted from bundle artifacts instead of requiring local package.json and manifest files. This enables publishing applications from any directory in CI/CD pipelines without maintaining the full project structure.

    New capabilities:

    • Extract app information from bundle's metadata.json
    • Validate app registration using artifact metadata when bundle path is provided
    • Maintain backward compatibility with existing package.json-based validation

    Usage:

    # Traditional validation (unchanged)
    fusion-framework-cli app publish
    
    # New artifact-based validation
    fusion-framework-cli app publish ./app-bundle.zip

    This resolves the limitation where applications could only be published from directories containing the source package.json, enabling more flexible CI/CD deployment scenarios.

Patch Changes