Dial 1.40 preparation (#446)

Co-authored-by: sdryapko <sdryapko2@gmail.com>
Co-authored-by: daryapyskwork <darya_pysk@epam.com>
Co-authored-by: Uladzislau Vishneuski <Vladisavvv@gmail.com>
Co-authored-by: Ilya Bondar <ilya_bondar@epam.com>
Co-authored-by: Palina_Kryvasheyeva <Palina_Kryvasheyeva@epam.com>
Co-authored-by: Daniil Yarmalkevich <daniil_yarmalkevich@epam.com>
Co-authored-by: Yury Kamiakou <yury_kamiakou@epam.com>
Co-authored-by: Siarhei Fedziukovich <Siarhei_Fedziukovich@epam.com>

Author: 9 people

docs/img/file_manager.gif

@@ -0,0 +1,37 @@
+# Release Notes
+
+The purpose of this document is to provide a quick summary of all the biggest new features added in this version and provide some additional description, video, or tutorials for major features.
+
+## Brief Summary
+
+The highlights of this release include a total redesign of DIAL's **File Manager**, initial support for **HuggingFace Model Servings** in the DIAL Admin, quality-of-life enhancements to DIAL Chat including **keyboard shortcuts**, and major upgrades within **DIAL's adapters.** 
+
+[![Release Notes January 2026](https://i3.ytimg.com/vi/QJSAFszBUlg/hqdefault.jpg)](https://www.youtube.com/watch?v=QJSAFszBUlg)
+
+## Major Enhancements
+
+**Improved File Management**: DIAL has supported uploading attachments into your conversations and applications for years, but in this release, we made tasks like moving, renaming, downloading, and cleaning up these uploaded files from your DIAL instance far more intuitive for end-users. Files can be dragged-and-dropped into the DIAL UI and into conversations with agents, automatically organized into appropriate folders, then easily renamed later if you so choose. Whether it's retrieving information from unstructured documents or uploading complex presentations and asking for suggestions, if chatting with documents is an important part of your AI journey, DIAL's new file manager makes this much easier. 
+
+<img src="../../img/file_manager.gif" width="357"/>
+
+**HuggingFace Model Servings**: DIAL's Adapter framework has always made connecting existing Open Source or other self-hosted models possible within DIAL. Many clients have expressed interest in deploying models directly within their DIAL ecosystem, to make it easier to manage and provide additional levels of control and flexibility. Support for NVIDIA NIM models has been available since Q4 2025, and in this release, we have added initial preview support for HuggingFace models as well. While it is still in preview mode, this feature allows system administrators to roll out open source models directly within their DIAL ecoystem.
+
+**Security Enhancements**: A simple but important security feature in this release allows administrators to set restrict API Keys to certain client IP address ranges. This restriction can be applied on a global level or to individual API Keys, and allows DIAL clients an additional level of control for limiting programmatic access to their DIAL instances. Additionally, we have added support of private CAs and self-signed certificates to DIAL's OpenAI Adapter.
+
+**Keyboard Shortcuts**: In addition to the file manager, end-user quality of life has also been improved with support for keyboard shortcuts in the user settings. In this release, the only settings are about configuring 'Enter' behavior for new lines vs. sending messages, but we plan on implementing additional key binding capabilities in the future. Providing a flexible and customizable platform fully within the owner's control has always been a key principle of DIAL, and this small QOL enhancement brings us, and clients, closer to this vision.
+
+![keyboard shortcuts](../../img/keyboard_shortcuts.png)
+
+**Anthropic Adapter**: Working with Anthropic's Claude has long been supported through AWS Bedrock and Gemini Vertex adapters, but the DIAL team decided it's time to release a native, cloud-agnostic adapter for Anthropic model types. We have released an adapter from DIAL's Chat Completion API to Claude's Messages API. Source code can be found here: https://github.com/epam/ai-dial-adapter-anthropic. This means that Claude is now supported regardless of the cloud vendor of choice, including Azure Foundry as well.
+
+**More Video Generation**: Google DeepMind's Veo 3 and Veo 3.1 models are now available through the Vertex adapter. This provides an alternative to OpenAI's Sora for video generation capabilities within DIAL, and we encourage all clients to test out their inner creativity with these models!
+
+<img src="../../img/veo_logo.gif" width="357"/>
+
+## Additional Notes
+
+For full technical release notes with all bug fixes and additional features, please consult the [upgrade guide](upgrade-to-1.40.md) with all the tags for each component, as well as the DIAL documentation.
+
+* **Gemini Adapter:** Added support for Google's server-side Python code interpreter in Gemini adapter
+* **Gemini Adapter:**  Added support for gemini-3-pro-preview model
+* **Admin Panel Autoscaling**: Added support for autoscaling of Admin Panel deployments, making configuration of the DIAL Admin easier.

docs/img/keyboard_shortcuts.png

@@ -0,0 +1,140 @@
+# Instructions
+
+## Versions
+
+1. Helm chart versions:
+   - dial: `5.20.0`
+   - dial-core: `4.3.1`
+   - dial-extension: `1.3.3`
+   - dial-admin: `0.8.0`
+2. Main components versions:
+   - ai-dial-adapter-bedrock: `0.36.3`
+   - ai-dial-adapter-openai: `0.36.1`
+   - ai-dial-adapter-vertexai: `0.32.0`
+   - ai-dial-adapter-dial: `0.11.0`
+   - ai-dial-auth-helper: `0.4.0`
+   - ai-dial-chat-themes: `0.13.0`
+   - ai-dial-chat: `0.42.2`
+   - ai-dial-core: `0.40.0`
+   - ai-dial-analytics-realtime: `0.20.2`
+   - ai-dial-rag: `0.39.0`
+   - ai-dial-log-parser: `0.3.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` (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-admin-deployment-manager-backend: `0.13.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.
+
+### Release-specific notes
+
+## Config changes
+
+### ai-dial-core
+
+
+### ai-dial-chat
+
+### ai-dial-chat-themes
+
+### 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
+
+#### Deployment manager FE configuration changes
+
+-  Set `DEPLOYMENTS_ENABLED` to `true` to see the Deployment Manager.
+-  `DISABLE_MENU_ITEMS`: add ModelDeployments to hide the Model Deployments UI when model serving infrastructure is not ready.
+- `EMBEDDED_APPS` — removed, no longer used.
+- `DEPLOYMENTS_PLUGIN_ENABLED` — removed, no longer used.
+  
+
+### 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
+  - azure provider - https://github.com/epam/ai-dial-admin-backend/blob/development/docs/azure-s2s-config.md
+ 
+### ai-dial-admin-deployment-manager-backend
+
+- Deployment manager: migrate to open source epam/ai-dial-admin-deployment-manager-backend:0.13.1
+- Proxy images for deployment manager migrate to opensource: https://github.com/epam/ai-dial-deployment-manager-mcp-proxy. Replace `MCP_PROXY_EXECUTABLE_IMAGE_ALPINE` with  `ghcr.io/epam/ai-dial-deployment-manager-mcp-proxy:0.1.0-alpine` and `MCP_PROXY_EXECUTABLE_IMAGE_DEBIAN` with  `ghcr.io/epam/ai-dial-deployment-manager-mcp-proxy:0.1.0-debian`
+
+#### Changes made to environment variables
+
+|Previous Variable Name|New Variable Name|Description|
+|-|-|-|
+|`SECURITY_ALLOWED_ROLES`|`providers.<your_provider_name>.allowed-roles`|Comma-separated list of roles with access permissions defined for the specific identity provider.|
+|`SECURITY_JWT_JWKS_URI`|`providers.<your_provider_name>.jwk-set-uri`|URI for JSON Web Key Set defined for the specific identity provider.|
+|`SECURITY_JWT_ACCEPTED_ISSUERS`|`providers.<your_provider_name>.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.<your_provider_name>.audiences`|Previously used as a unique identifier of the DIAL Admin Deployment Manager application. This environment variable was removed bacause it defined the same property as `SECURITY_JWT_ACCEPTED_AUDIENCES`.|
+|`SECURITY_JWT_ACCEPTED_AUDIENCES`|`providers.<your_provider_name>.audiences`|List of accepted JWT token audiences. Defines the intended recipients of the claim `aud` in JWT.|
+|`SECURITY_ROLES_CLAIM`|`providers.<your_provider_name>.role-claims`|JWT claim name for user roles defined for the specific identity provider.|
+|`SECURITY_USER_CLAIM`|`providers.<your_provider_name>.principal-claim`|Specific claim that uniquely identifies the user or service (the "principal") for whom the token was issued.|
+
+**Note**: In this release, the following provider configuration properties have changed from optional to mandatory:
+* providers.<your_provider_name>.role-claims
+* providers.<your_provider_name>.principal-claim
+
+
+#### Added support for multiple identity providers
+
+The DIAL Admin Deployment Manager 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.principal-claim: "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.principal-claim: "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.principal-claim: "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"
+```
+
+#### Model Serving (Preview)
+
+A new **Model Serving (Preview)** feature has been introduced. When the underlying model serving infrastructure (KServe/NIM) are not yet available, configure the service with:
+
+- `K8S_NIM_ENABLED: "false"`
+- `K8S_KSERVE_ENABLED: "false"`
+
+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
+
+- Now docker image for `ai-dial-quickapps-backend` is published to [Docker Hub](https://hub.docker.com/r/epam/ai-dial-quickapps-backend). Update your Helm chart values to use the new image location if you were using a custom image registry before.
+