diff --git a/dial-samples/common-ui-app/package.json b/dial-samples/common-ui-app/package.json index 09cb48801..f7a0cd669 100644 --- a/dial-samples/common-ui-app/package.json +++ b/dial-samples/common-ui-app/package.json @@ -32,7 +32,7 @@ "@monaco-editor/react": "^4.7.0", "@tabler/icons-react": "^3.30.0", "classnames": "^2.5.1", - "lodash": "^4.17.23", + "lodash": "^4.18.0", "monaco-editor": "^0.52.2", "next": "~15.5.14", "next-auth": "^4.24.12", diff --git a/dial-samples/common-ui-app/yarn.lock b/dial-samples/common-ui-app/yarn.lock index 27130861d..ee28f988f 100644 --- a/dial-samples/common-ui-app/yarn.lock +++ b/dial-samples/common-ui-app/yarn.lock @@ -8307,11 +8307,16 @@ lodash.uniq@^4.5.0: resolved "https://registry.yarnpkg.com/lodash.uniq/-/lodash.uniq-4.5.0.tgz#d0225373aeb652adc1bc82e4945339a842754773" integrity sha512-xfBaXQd9ryd9dlSDvnvI0lvxfLJlYAZzXomUYzLKtUeOQvOP5piqAWuGtrhWeqaXK9hhoM/iyJc5AV+XfsX3HQ== -lodash@^4.17.21, lodash@^4.17.23: +lodash@^4.17.21: version "4.17.23" resolved "https://registry.yarnpkg.com/lodash/-/lodash-4.17.23.tgz#f113b0378386103be4f6893388c73d0bde7f2c5a" integrity sha512-LgVTMpQtIopCi79SJeDiP0TfWi5CNEc/L/aRdTh3yIvmZXTnheWpKjSZhnvMl8iXbC1tFg9gdHHDMLoV7CnG+w== +lodash@^4.18.0: + version "4.18.1" + resolved "https://registry.yarnpkg.com/lodash/-/lodash-4.18.1.tgz#ff2b66c1f6326d59513de2407bf881439812771c" + integrity sha512-dMInicTPVE8d1e5otfwmmjlxkZoUpiVLwyeTdUsi/Caj/gfzzblBcCE5sRHV/AsjuCmxWrte2TNGSYuCeCq+0Q== + log-symbols@^4.0.0: version "4.1.0" resolved "https://registry.yarnpkg.com/log-symbols/-/log-symbols-4.1.0.tgz#3fbdbb95b4683ac9fc785111e792e558d4abd503" diff --git a/docs/releases/1.38/upgrade-to-1.38.md b/docs/releases/1.38/upgrade-to-1.38.md index 02e47c7b2..3e3431510 100644 --- a/docs/releases/1.38/upgrade-to-1.38.md +++ b/docs/releases/1.38/upgrade-to-1.38.md @@ -1,160 +1,160 @@ -# Instructions - -## Versions - -1. Helm chart versions: - - dial: `5.18.0` - - dial-core: `4.3.1` - - dial-extension: `1.3.3` - - dial-admin: `0.6.0` -2. Main components versions: - - ai-dial-adapter-bedrock: `0.35.0` - - ai-dial-adapter-openai: `0.34.0` - - ai-dial-adapter-vertexai: `0.29.0` - - ai-dial-adapter-dial: `0.10.0` - - ai-dial-auth-helper: `0.4.0` - - ai-dial-chat-themes: `0.12.0` - - ai-dial-chat: `0.40.6` - - ai-dial-core: `0.38.0` - - ai-dial-analytics-realtime: `0.19.4` - - ai-dial-rag: `0.36.0` - - ai-dial-log-parser: `0.2.0` - - ai-dial-code-interpreter: `0.2.0` - - ai-dial-app-controller: `0.3.0` - - ai-dial-app-builder-python: `0.1.0` - - quick-apps: `0.8.2` - - quick-apps-2.0: `0.2.0` - - mindmap-backend: `0.11.6` - - mindmap-frontend: `0.8.13` - - admin-backend: `0.11.2` - - admin-frontend: `0.11.2` - - ai-dial-admin-mcp-manager-backend: `0.2.2` - - ai-dial-admin-mcp-manager-frontend: `0.2.1` - -## Before upgrade - -### General notes - -- Please review the [Config changes](#config-changes) chapter carefully for each component that is used in your DIAL installation. Changes in components' configuration may be required. -- Please check if any image tag overrides (`image.tag`) are present and remove them if they are not required anymore. -- Please check and add `image.repository` to change the image location for `redis`, `postgresql`, `keycloak` and `keycloakConfigCli` components to start using alternative Docker registries (e.g. Amazon ECR Public Gallery) if required. -- Verify `COMPATIBILITY_MAPPING` parameter of DIAL Adapters which are used in your DIAL installation and remove mappings for models that are natively supported by the adapters. - -### Release-specific notes - -If DIAL Admin Panel is used for managing the DIAL Core configuration, please consider the following order of updating the DIAL components: - -1. Update DIAL Admin Panel using `dial-admin` Helm chart with the following parameters being set: - 1. Disable `ENABLE_CORE_CONFIG_VERSION_AUTO_DETECT`. - 2. Set `CORE_CONFIG_VERSION` to the version of DIAL Core you are going to update to (e.g. `0.38.0`). -2. Update DIAL using `dial` Helm chart. -3. Enable `ENABLE_CORE_CONFIG_VERSION_AUTO_DETECT` and disable `CORE_CONFIG_VERSION` parameters of DIAL Admin Panel. - -## Config changes - -### ai-dial-core - -Changes in [DIAL Core](https://github.com/epam/ai-dial-core) configuration: - -|Parameter|Required|Description| -|-|-|-| -|`supportCommentInRateResponse`|No|When enabled, it allows users to include a text comment along with their like/dislike feedback for this deployment. The comment is sent in the `comment` field of the rate response payload.| -|`globalInterceptors`|No|A list of [interceptors](https://github.com/epam/ai-dial-core/blob/development/docs/dynamic-settings/interceptors.md#local-interceptors) applicable for any deployment on you DIAL setup.| -|`dial:applicationTypeInterceptors`|No|A field that can be added to the application's JSON schema. This field can include a list of [interceptors](https://github.com/epam/ai-dial-core/blob/development/docs/dynamic-settings/interceptors.md#application-type-interceptors) that will apply to all applications created based on this schema.| -|`applications.features.addonsSupported`|No|The flag `addonsSupported` is removed from application's features.| -|`models.features.addonsSupported`|No|The flag `addonsSupported` is removed from model's features.| -|`addons`|No|The section is removed from the DIAL Core config.| -|`assistant`|No|The section is removed from the DIAL Core config.| - -### ai-dial-chat - -Changes in [DIAL Chat](https://github.com/epam/ai-dial-chat/blob/development/apps/chat/README.md) configuration: - -|Parameter|Required|Description| -|-|-|-| -|`code-interpreter`|No|Include this feature in [`ENABLED_FEATURES`](https://github.com/epam/ai-dial-chat/blob/development/libs/shared/src/types/features.ts) [environment variable](https://github.com/epam/ai-dial-chat/blob/development/apps/chat/README.md#environment-variables) to enable Code Interpreter on the current DIAL setup.| -|`dislike-comment`|No|Include this feature in [`ENABLED_FEATURES`](https://github.com/epam/ai-dial-chat/blob/development/libs/shared/src/types/features.ts) [environment variable](https://github.com/epam/ai-dial-chat/blob/development/apps/chat/README.md#environment-variables) to enable sending a comment in addition to a dislike feedback in the chat message.| - -### ai-dial-chat-themes - -Changes in [DIAL Chat Themes](https://github.com/epam/ai-dial-chat-themes) configuration: - -- Icons were added for RAG (RAG_files_search.svg) and Echo (Echo.svg). -- The default icon was added for Toolsets (default-toolset.svg). -- The default icon for Addons (Addon_Wolfram.svg) was removed. - -### ai-dial-adapter-openai - -Changes in [DIAL OpenAI Adapter](https://github.com/epam/ai-dial-adapter-openai) configuration: - -|Variable|Required|Default|Description| -|-|-|-|-| -|`AUDIO_AZURE_API_VERSION`|No|`2025-03-01-preview`|Include this [environment variable](https://github.com/epam/ai-dial-adapter-openai?tab=readme-ov-file#environment-variables) to specify the API version for requests to the [Azure Audio API](https://github.com/epam/ai-dial-adapter-openai?tab=readme-ov-file#azure-audio-api) endpoints.| - -### ai-dial-adapter-bedrock - -Changes in [DIAL Bedrock Adapter](https://github.com/epam/ai-dial-adapter-bedrock) configuration: - -|Variable|Required|Description| -|-|-|-| -|`AWS_SESSION_TOKEN`|No|Include this [environment variable](https://github.com/epam/ai-dial-adapter-bedrock?tab=readme-ov-file#environment-variables) to add an alternative way to specify access credentials for the Bedrock service.| - -- [Removed support](https://github.com/epam/ai-dial-adapter-bedrock/pull/335) of retired AI21 and Stability AI models. These models **MUST** be deleted from the adapter configuration before upgrade. - -### ai-dial-adapter-vertexai - -- Removed support of retired Gemini 1.5 models ([#309](https://github.com/epam/ai-dial-adapter-vertexai/pull/309), [#315](https://github.com/epam/ai-dial-adapter-vertexai/pull/315)). These models **MUST** be deleted from the adapter configuration before upgrade. - -### admin-frontend - -Changes in [DIAL Admin Frontend](https://github.com/epam/ai-dial-admin-frontend) configuration: - -- The [environment variable](https://github.com/epam/ai-dial-admin-frontend?tab=readme-ov-file#environment-variables) `THEMES_CONFIG_IMAGES` was removed. - -### admin-backend - -Changes in [DIAL Admin Backend](https://github.com/epam/ai-dial-admin-backend) configuration: - -#### Changes made to environment variables - -|Previous Variable Name|New Variable Name|Description| -|-|-|-| -|`SECURITY_ALLOWED_ROLES`|`providers..allowed-roles`|Comma-separated list of roles with access permissions defined for the specific identity provider.| -|`SECURITY_JWT_JWKS_URI`|`providers..jwk-set-uri`|URI for JSON Web Key Set defined for the specific identity provider.| -|`SECURITY_JWT_ACCEPTED_ISSUERS`|`providers..issuer`|List of accepted JWT token issuers defined for the specific identity provider.| -|`SECURITY_JWT_ACCEPTED_ISSUERS_ALIAS`|`providers.azure.aliases`|Aliases for accepted JWT token issuers (applicable only for Azure provider).| -|`DIAL_ADMIN_CLIENT_ID`|`providers..audiences`|Previously used as a unique identifier of the DIAL Admin backend application. This environment variable was removed bacause it defined the same property as `SECURITY_JWT_ACCEPTED_AUDIENCES`.| -|`SECURITY_JWT_ACCEPTED_AUDIENCES`|`providers..audiences`|List of accepted JWT token audiences. Defines the intended recipients of the claim `aud` in JWT.| -|`SECURITY_ROLES_CLAIM`|`providers..role-claims`|JWT claim name for user roles defined for the specific identity provider.| - -#### Added support for multiple identity providers - -The DIAL Admin application now supports the use of multiple identity providers, which offers greater flexibility and integration with various identity services. Below is an example of configuration demonstrating how to set up multiple providers: - -```properties -providers.auth0.jwk-set-uri: "https://example-auth0.com/.well-known/jwks.json" -providers.auth0.issuer: "https://example-auth0.com" -providers.auth0.role-claims: "example_roles" -providers.auth0.audiences: "example-audience-id" -providers.keycloak.jwk-set-uri: "https://example-keycloak.com/realms/Example/protocol/openid-connect/certs" -providers.keycloak.issuer: "https://example-keycloak.com/realms/Example" -providers.keycloak.role-claims: "example_roles" -providers.keycloak.audiences: "example-ui, example-admin" -providers.azure.jwk-set-uri: "https://example.microsoft.com/common/discovery/v2.0/keys" -providers.azure.issuer: "example-issuer-id" -providers.azure.role-claims: "example_groups" -providers.azure.audiences: "example-audience-id" -providers.azure.aliases: "login.microsoftonline.com, login.windows.net, login.microsoft.com, sts.windows.net, login.partner.microsoftonline.cn, login.chinacloudapi.cn, login.microsoftonline.de, login.microsoftonline.us, login.usgovcloudapi.net, login-us.microsoftonline.com" -providers.azure.allowed-roles: "example-role-id" -``` -#### Detect dial-core versions changes - -1. **Mandatory `CORE_CONFIG_VERSION`**: - -The `CORE_CONFIG_VERSION` environment variable is now **required** to be set in case `ENABLE_CORE_CONFIG_VERSION_AUTO_DETECT` is set to `false`. To resolve any breaking changes in the DIAL Core JSON config (e.g. the deletion of any property), it is recommended to define `CORE_CONFIG_VERSION` environment variable even if `ENABLE_CORE_CONFIG_VERSION_AUTO_DETECT` is set to `true`. - -2. **Handling of breaking changes in DIAL Core configuration**: - -If a non-compatible JSON configuration is used with dial-core, the dial-admin application will not be able to start and connect with it to retrieve its config version. If the connection to the dial-core application cannot be established, the dial-admin application will apply the configuration version specified in the `CORE_CONFIG_VERSION` environment variable. - - +# Instructions + +## Versions + +1. Helm chart versions: + - dial: `5.18.0` + - dial-core: `4.3.1` + - dial-extension: `1.3.3` + - dial-admin: `0.6.0` +2. Main components versions: + - ai-dial-adapter-bedrock: `0.35.0` + - ai-dial-adapter-openai: `0.34.0` + - ai-dial-adapter-vertexai: `0.29.0` + - ai-dial-adapter-dial: `0.10.0` + - ai-dial-auth-helper: `0.4.0` + - ai-dial-chat-themes: `0.12.0` + - ai-dial-chat: `0.40.6` + - ai-dial-core: `0.38.0` + - ai-dial-analytics-realtime: `0.19.4` + - ai-dial-rag: `0.36.0` + - ai-dial-log-parser: `0.2.0` + - ai-dial-code-interpreter: `0.2.0` + - ai-dial-app-controller: `0.3.0` + - ai-dial-app-builder-python: `0.1.0` + - ai-dial-quick-apps: `0.8.2` + - ai-dial-quick-apps-2.0: `0.2.0` + - ai-dial-mindmap-backend: `0.11.6` + - ai-dial-mindmap-frontend: `0.8.13` + - ai-dial-admin-backend: `0.11.2` + - ai-dial-admin-frontend: `0.11.2` + - ai-dial-admin-mcp-manager-backend: `0.2.2` + - ai-dial-admin-mcp-manager-frontend: `0.2.1` + +## Before upgrade + +### General notes + +- Please review the [Config changes](#config-changes) chapter carefully for each component that is used in your DIAL installation. Changes in components' configuration may be required. +- Please check if any image tag overrides (`image.tag`) are present and remove them if they are not required anymore. +- Please check and add `image.repository` to change the image location for `redis`, `postgresql`, `keycloak` and `keycloakConfigCli` components to start using alternative Docker registries (e.g. Amazon ECR Public Gallery) if required. +- Verify `COMPATIBILITY_MAPPING` parameter of DIAL Adapters which are used in your DIAL installation and remove mappings for models that are natively supported by the adapters. + +### Release-specific notes + +If DIAL Admin Panel is used for managing the DIAL Core configuration, please consider the following order of updating the DIAL components: + +1. Update DIAL Admin Panel using `dial-admin` Helm chart with the following parameters being set: + 1. Disable `ENABLE_CORE_CONFIG_VERSION_AUTO_DETECT`. + 2. Set `CORE_CONFIG_VERSION` to the version of DIAL Core you are going to update to (e.g. `0.38.0`). +2. Update DIAL using `dial` Helm chart. +3. Enable `ENABLE_CORE_CONFIG_VERSION_AUTO_DETECT` and disable `CORE_CONFIG_VERSION` parameters of DIAL Admin Panel. + +## Config changes + +### ai-dial-core + +Changes in [DIAL Core](https://github.com/epam/ai-dial-core) configuration: + +|Parameter|Required|Description| +|-|-|-| +|`supportCommentInRateResponse`|No|When enabled, it allows users to include a text comment along with their like/dislike feedback for this deployment. The comment is sent in the `comment` field of the rate response payload.| +|`globalInterceptors`|No|A list of [interceptors](https://github.com/epam/ai-dial-core/blob/development/docs/dynamic-settings/interceptors.md#local-interceptors) applicable for any deployment on you DIAL setup.| +|`dial:applicationTypeInterceptors`|No|A field that can be added to the application's JSON schema. This field can include a list of [interceptors](https://github.com/epam/ai-dial-core/blob/development/docs/dynamic-settings/interceptors.md#application-type-interceptors) that will apply to all applications created based on this schema.| +|`applications.features.addonsSupported`|No|The flag `addonsSupported` is removed from application's features.| +|`models.features.addonsSupported`|No|The flag `addonsSupported` is removed from model's features.| +|`addons`|No|The section is removed from the DIAL Core config.| +|`assistant`|No|The section is removed from the DIAL Core config.| + +### ai-dial-chat + +Changes in [DIAL Chat](https://github.com/epam/ai-dial-chat/blob/development/apps/chat/README.md) configuration: + +|Parameter|Required|Description| +|-|-|-| +|`code-interpreter`|No|Include this feature in [`ENABLED_FEATURES`](https://github.com/epam/ai-dial-chat/blob/development/libs/shared/src/types/features.ts) [environment variable](https://github.com/epam/ai-dial-chat/blob/development/apps/chat/README.md#environment-variables) to enable Code Interpreter on the current DIAL setup.| +|`dislike-comment`|No|Include this feature in [`ENABLED_FEATURES`](https://github.com/epam/ai-dial-chat/blob/development/libs/shared/src/types/features.ts) [environment variable](https://github.com/epam/ai-dial-chat/blob/development/apps/chat/README.md#environment-variables) to enable sending a comment in addition to a dislike feedback in the chat message.| + +### ai-dial-chat-themes + +Changes in [DIAL Chat Themes](https://github.com/epam/ai-dial-chat-themes) configuration: + +- Icons were added for RAG (RAG_files_search.svg) and Echo (Echo.svg). +- The default icon was added for Toolsets (default-toolset.svg). +- The default icon for Addons (Addon_Wolfram.svg) was removed. + +### ai-dial-adapter-openai + +Changes in [DIAL OpenAI Adapter](https://github.com/epam/ai-dial-adapter-openai) configuration: + +|Variable|Required|Default|Description| +|-|-|-|-| +|`AUDIO_AZURE_API_VERSION`|No|`2025-03-01-preview`|Include this [environment variable](https://github.com/epam/ai-dial-adapter-openai?tab=readme-ov-file#environment-variables) to specify the API version for requests to the [Azure Audio API](https://github.com/epam/ai-dial-adapter-openai?tab=readme-ov-file#azure-audio-api) endpoints.| + +### ai-dial-adapter-bedrock + +Changes in [DIAL Bedrock Adapter](https://github.com/epam/ai-dial-adapter-bedrock) configuration: + +|Variable|Required|Description| +|-|-|-| +|`AWS_SESSION_TOKEN`|No|Include this [environment variable](https://github.com/epam/ai-dial-adapter-bedrock?tab=readme-ov-file#environment-variables) to add an alternative way to specify access credentials for the Bedrock service.| + +- [Removed support](https://github.com/epam/ai-dial-adapter-bedrock/pull/335) of retired AI21 and Stability AI models. These models **MUST** be deleted from the adapter configuration before upgrade. + +### ai-dial-adapter-vertexai + +- Removed support of retired Gemini 1.5 models ([#309](https://github.com/epam/ai-dial-adapter-vertexai/pull/309), [#315](https://github.com/epam/ai-dial-adapter-vertexai/pull/315)). These models **MUST** be deleted from the adapter configuration before upgrade. + +### ai-dial-admin-frontend + +Changes in [DIAL Admin Frontend](https://github.com/epam/ai-dial-admin-frontend) configuration: + +- The [environment variable](https://github.com/epam/ai-dial-admin-frontend?tab=readme-ov-file#environment-variables) `THEMES_CONFIG_IMAGES` was removed. + +### ai-dial-admin-backend + +Changes in [DIAL Admin Backend](https://github.com/epam/ai-dial-admin-backend) configuration: + +#### Changes made to environment variables + +|Previous Variable Name|New Variable Name|Description| +|-|-|-| +|`SECURITY_ALLOWED_ROLES`|`providers..allowed-roles`|Comma-separated list of roles with access permissions defined for the specific identity provider.| +|`SECURITY_JWT_JWKS_URI`|`providers..jwk-set-uri`|URI for JSON Web Key Set defined for the specific identity provider.| +|`SECURITY_JWT_ACCEPTED_ISSUERS`|`providers..issuer`|List of accepted JWT token issuers defined for the specific identity provider.| +|`SECURITY_JWT_ACCEPTED_ISSUERS_ALIAS`|`providers.azure.aliases`|Aliases for accepted JWT token issuers (applicable only for Azure provider).| +|`DIAL_ADMIN_CLIENT_ID`|`providers..audiences`|Previously used as a unique identifier of the DIAL Admin backend application. This environment variable was removed bacause it defined the same property as `SECURITY_JWT_ACCEPTED_AUDIENCES`.| +|`SECURITY_JWT_ACCEPTED_AUDIENCES`|`providers..audiences`|List of accepted JWT token audiences. Defines the intended recipients of the claim `aud` in JWT.| +|`SECURITY_ROLES_CLAIM`|`providers..role-claims`|JWT claim name for user roles defined for the specific identity provider.| + +#### Added support for multiple identity providers + +The DIAL Admin application now supports the use of multiple identity providers, which offers greater flexibility and integration with various identity services. Below is an example of configuration demonstrating how to set up multiple providers: + +```properties +providers.auth0.jwk-set-uri: "https://example-auth0.com/.well-known/jwks.json" +providers.auth0.issuer: "https://example-auth0.com" +providers.auth0.role-claims: "example_roles" +providers.auth0.audiences: "example-audience-id" +providers.keycloak.jwk-set-uri: "https://example-keycloak.com/realms/Example/protocol/openid-connect/certs" +providers.keycloak.issuer: "https://example-keycloak.com/realms/Example" +providers.keycloak.role-claims: "example_roles" +providers.keycloak.audiences: "example-ui, example-admin" +providers.azure.jwk-set-uri: "https://example.microsoft.com/common/discovery/v2.0/keys" +providers.azure.issuer: "example-issuer-id" +providers.azure.role-claims: "example_groups" +providers.azure.audiences: "example-audience-id" +providers.azure.aliases: "login.microsoftonline.com, login.windows.net, login.microsoft.com, sts.windows.net, login.partner.microsoftonline.cn, login.chinacloudapi.cn, login.microsoftonline.de, login.microsoftonline.us, login.usgovcloudapi.net, login-us.microsoftonline.com" +providers.azure.allowed-roles: "example-role-id" +``` +#### Detect dial-core versions changes + +1. **Mandatory `CORE_CONFIG_VERSION`**: + +The `CORE_CONFIG_VERSION` environment variable is now **required** to be set in case `ENABLE_CORE_CONFIG_VERSION_AUTO_DETECT` is set to `false`. To resolve any breaking changes in the DIAL Core JSON config (e.g. the deletion of any property), it is recommended to define `CORE_CONFIG_VERSION` environment variable even if `ENABLE_CORE_CONFIG_VERSION_AUTO_DETECT` is set to `true`. + +2. **Handling of breaking changes in DIAL Core configuration**: + +If a non-compatible JSON configuration is used with dial-core, the dial-admin application will not be able to start and connect with it to retrieve its config version. If the connection to the dial-core application cannot be established, the dial-admin application will apply the configuration version specified in the `CORE_CONFIG_VERSION` environment variable. + + diff --git a/docs/releases/1.39/upgrade-to-1.39.md b/docs/releases/1.39/upgrade-to-1.39.md index 2e9ef385a..35c017742 100644 --- a/docs/releases/1.39/upgrade-to-1.39.md +++ b/docs/releases/1.39/upgrade-to-1.39.md @@ -22,12 +22,12 @@ - ai-dial-code-interpreter: `0.2.0` - ai-dial-app-controller: `0.3.0` - ai-dial-app-builder-python: `0.1.0` - - quick-apps: `0.8.2` - - quick-apps-2.0: `0.3.1` - - mindmap-backend: `0.12.6` - - mindmap-frontend: `0.9.8` - - admin-backend: `0.12.0` - - admin-frontend: `0.12.4` + - ai-dial-quick-apps: `0.8.2` + - ai-dial-quick-apps-2.0: `0.3.1` + - ai-dial-mindmap-backend: `0.12.6` + - ai-dial-mindmap-frontend: `0.9.8` + - ai-dial-admin-backend: `0.12.0` + - ai-dial-admin-frontend: `0.12.4` - ai-dial-admin-mcp-manager-backend ->ai-dial-admin-deployment-manager-backend: `0.3.1` ## Before upgrade @@ -53,10 +53,6 @@ Added new optional env variables `NEXT_PUBLIC_STAGE_CONTENT_LIMIT` - Sets the maximum size (in kilobytes) for stage content when rendered. If the content exceeds this limit, a download link will be shown instead. Default value is 40. -### ai-dial-chat-themes - -### ai-dial-adapter-openai - ### ai-dial-adapter-bedrock Added new optional env variables @@ -89,9 +85,7 @@ ANTHROPIC_MAX_RETRY_ATTEMPTS=2 GOOGLE_GENAI_MAX_RETRY_ATTEMPTS=4 ``` -### admin-frontend - -### admin-backend +### ai-dial-admin-backend #### Detect dial-core versions changes @@ -112,11 +106,11 @@ Environment variables to configure embeddings thread pools DIAL_RAG**CPU_POOLS** IMPORTANT (!!!) The Deployment Manager FE is part of the Administration application FE. -### Mind Map +### ai-dial-mind-map The migration guide: -### quick-apps-2.0 +### ai-dial-quick-apps-2.0 Update schema to the recent one: [Quickapp2 Schema](./quickapp2-schema.json). Changes were done in `$defs` and `properties` sections. Use admin panel to update existing quick apps to the recent schema version. diff --git a/docs/releases/1.40/upgrade-to-1.40.md b/docs/releases/1.40/upgrade-to-1.40.md index e27d34ce9..57e2c23d4 100644 --- a/docs/releases/1.40/upgrade-to-1.40.md +++ b/docs/releases/1.40/upgrade-to-1.40.md @@ -22,12 +22,12 @@ - ai-dial-code-interpreter: `0.2.0` - ai-dial-app-controller: `0.3.0` - ai-dial-app-builder-python: `0.1.0` - - quick-apps: `0.8.2` (deprecated, use ai-dial-quickapps-backend for new installations) + - ai-dial-quick-apps: `0.8.2` (deprecated, use ai-dial-quickapps-backend for new installations) - ai-dial-quickapps-backend: `0.4.0` (earlier known as quick-apps-2.0) - - mindmap-backend: `0.13.0` - - mindmap-frontend: `0.9.13` - - admin-backend: `0.13.0` - - admin-frontend: `0.13.4` + - ai-dial-mind-map-backend: `0.13.0` + - ai-dial-mindmap-frontend: `0.9.13` + - ai-dial-admin-backend: `0.13.0` + - ai-dial-admin-frontend: `0.13.4` - ai-dial-admin-deployment-manager-backend: `0.13.1` ## Before upgrade @@ -42,24 +42,15 @@ ## Config changes -### ai-dial-core - - -### ai-dial-chat - ### ai-dial-chat-themes Added new button colors. If you are using a custom theme, please add the new color definitions to your theme configuration. (https://github.com/epam/ai-dial-chat-themes/blob/development/docs/CHANGELOG.md#0130) -### ai-dial-adapter-openai - -### ai-dial-adapter-bedrock - ### ai-dial-adapter-vertexai - Deprecation of COMPATIBILITY_MAPPING env var in favour of per-upstream configuration (https://github.com/epam/ai-dial-adapter-vertexai?tab=readme-ov-file#compatibility-configuration-in-dial-core-config) -### admin-frontend +### ai-dial-admin-frontend #### Deployment manager FE configuration changes @@ -69,7 +60,7 @@ Added new button colors. If you are using a custom theme, please add the new col - `DEPLOYMENTS_PLUGIN_ENABLED` — removed, no longer used. -### admin-backend +### ai-dial-admin-backend #### S2S Admin Backend and core configuration Here is the full instraction for dial admin s2s configuration : - keycloack provider - https://github.com/epam/ai-dial-admin-backend/blob/development/docs/keycloack-s2s.md @@ -131,9 +122,6 @@ A new **Model Serving (Preview)** feature has been introduced. When the underlyi These settings ensure the service operates correctly in environments where model serving components are not yet ready or deployed. -### ai-dial-rag - -### Mind Map ### ai-dial-quickapps-backend diff --git a/docs/releases/1.41/upgrade-to-1.41.md b/docs/releases/1.41/upgrade-to-1.41.md index 150352fcd..a85a0e67d 100644 --- a/docs/releases/1.41/upgrade-to-1.41.md +++ b/docs/releases/1.41/upgrade-to-1.41.md @@ -23,8 +23,8 @@ - ai-dial-app-controller: `0.4.0` - ai-dial-app-builder-python: `0.1.0` - ai-dial-quickapps-backend: `0.5.2` - - dial-mind-map-backend: `0.13.2` - - dial-mind-map-frontend: `0.9.15` + - ai-dial-mind-map-backend: `0.13.2` + - ai-dial-mind-map-frontend: `0.9.15` - ai-dial-admin-backend: `0.14.3` - ai-dial-admin-frontend: `0.14.5` - ai-dial-admin-deployment-manager-backend: `0.14.3` @@ -69,9 +69,6 @@ For more details of changes, see the [changelog](https://github.com/epam/ai-dial ### ai-dial-chat-themes Added new button colors and rename color tokens. If you are using a custom theme, please add the new color definitions to your theme configuration. For more details of changes, see the [changelog](https://github.com/epam/ai-dial-chat-themes/tree/0.14.0/docs/CHANGELOG.md#0140). - -### ai-dial-adapter-openai - ### ai-dial-adapter-bedrock #### Deprecated Environment Variable @@ -80,9 +77,8 @@ Added new button colors and rename color tokens. If you are using a custom theme |----------------------------|---------------|------------| | `COMPATIBILITY_MAPPING` | `{}` | **Deprecated** in favor of [compatibility configuration in DIAL Core config](https://github.com/epam/ai-dial-adapter-bedrock/tree/0.37.0?tab=readme-ov-file#compatibility-configuration-in-dial-core-config). For more details of changes, see [Adapter Bedrock Environment Variables](https://github.com/epam/ai-dial-adapter-bedrock/tree/0.37.0?tab=readme-ov-file#environment-variables) section. | -### ai-dial-adapter-vertexai -### admin-frontend +### ai-dial-admin-frontend Requires `ai-dial-chat-themes` **v0.14.0 or higher** For more details of changes, see the [changelog](https://github.com/epam/ai-dial-chat-themes/tree/0.14.0/docs/CHANGELOG.md#0140). @@ -95,7 +91,7 @@ For more details of changes, see the [changelog](https://github.com/epam/ai-dial |----------------------|---------------|----------|------------|----------------| | `AUTH_IDTOKEN_PROVIDERS` | - | No | Comma-separated list of identity provider IDs that will pass an **identity token** to the API instead of an access token. This is required for providers whose access tokens are not JWT (e.g., Google, GitLab). | Any string. Values must be separated by commas (e.g., `google,gitlab`). | -### admin-backend +### ai-dial-admin-backend #### GCP Database Setup If you are using a **GCP Database**, follow the instructions in the [GCP Database Configuration Guide](https://github.com/epam/ai-dial-admin-backend/blob/0.14.2/docs/gcp-cloud-postgres.md) to set it up properly. @@ -220,12 +216,6 @@ The following environment variables were removed: If these variables are still present in your environment, they should be removed to avoid confusion. -### ai-dial-rag - -### Mind Map - -### ai-dial-app-controller - ### ai-dial-quickapps-backend * env variable `PREDEFINED_BASE_PATH` [was deprecated](https://github.com/epam/ai-dial-quickapps-backend/tree/0.5.2?tab=readme-ov-file#deprecated-environment-variables). Migrate to `PREDEFINED_EXTRA_PATHS` by renaming env variable and formatting value as json list, if needed (`value` -> `["value"]`). diff --git a/package-lock.json b/package-lock.json index 3b564a9aa..c1ce51381 100644 --- a/package-lock.json +++ b/package-lock.json @@ -10039,9 +10039,9 @@ } }, "node_modules/lodash": { - "version": "4.17.23", - "resolved": "https://registry.npmjs.org/lodash/-/lodash-4.17.23.tgz", - "integrity": "sha512-LgVTMpQtIopCi79SJeDiP0TfWi5CNEc/L/aRdTh3yIvmZXTnheWpKjSZhnvMl8iXbC1tFg9gdHHDMLoV7CnG+w==", + "version": "4.18.1", + "resolved": "https://registry.npmjs.org/lodash/-/lodash-4.18.1.tgz", + "integrity": "sha512-dMInicTPVE8d1e5otfwmmjlxkZoUpiVLwyeTdUsi/Caj/gfzzblBcCE5sRHV/AsjuCmxWrte2TNGSYuCeCq+0Q==", "license": "MIT" }, "node_modules/lodash.debounce": {