Major Enhancements
Identifying editors used for workspaces
The Workspaces list now includes an Editor column that displays an icon for the editor used by each workspace. You can hover over the icon to see a tooltip with the editor name. Eclipse Che determines the editor from the che.eclipse.org/che-editor workspace annotation and matches it against the editors registry to ensure accurate icons and labels. This improvement makes it easier to identify the configured editor for each workspace directly from the dashboard.
Viewing available Git branches in the User Dashboard
The User Dashboard now displays a list of available Git branches when you create a workspace in the Git Repo Options view. The dashboard retrieves the branches and displays them in a drop-down list in the Git Branch section, making selection easier and reducing errors. If the repository is private or branches cannot be retrieved, the workflow reverts to the existing behavior, allowing you to manually enter a branch name.
Updating branding for the application loader
The application loader now dynamically selects the most appropriate logo from available image formats, including JPG, JPEG, PNG, GIF, WebP, and SVG. Optimized rendering ensures sharper visuals across different environments.
Creating devfiles with a new web interface
A community-supported web application for creating devfiles through an interactive step-by-step wizard is now available at https://start.devfile.io/.
DevWorkspace Operator 0.39.0
DevWorkspace Operator 0.39.0 is now available, adding new functionality to Eclipse Che. For more information, see the changelog.
Supporting UBI 10 for the Universal Developer Image
A new Universal Developer Image (UDI) based on Universal Base Image 10 (UBI 10) is available at quay.io/devfile/universal-developer-image:ubi10-latest. This image includes updated developer tools for compatibility with UBI 10.
Configuring container resource caps
Administrators can now set maximum resource limits and requests for workspace containers using the spec.DevWorkspace.containerResourceCaps field in the CheCluster custom resource (CR). This prevents the creation of workspaces with excessive CPU or memory requirements at the devfile level. If a devfile exceeds the limit or request caps, the system automatically applies the capped values.
spec:
devEnvironments:
containerResourceCaps:
limits:
cpu: "1"
memory: 2Gi
requests:
cpu: "0.1"
memory: 100Mi
Managing extension installation with the vscode-editor-configurations ConfigMap
Administrators can control Che Code extension installation using the BlockCliExtensionsInstallation, BlockDefaultExtensionsInstallation, BlockInstallFromVSIXCommandExtensionsInstallation, and AllowedExtensions properties in the policy data file. For example, you can disable extension installation or activation. For more information, see Manage extension installation with ConfigMap.
Bug Fixes
Optimizing branding assets for performance
Branding logo and favicon loading is now optimized to eliminate unnecessary network requests and visual delays. Logo format detection is cached to prevent repeated 404 requests, and assets are loaded during the preload phase. Branding assets now appear immediately without waiting for full bootstrap or cluster configuration fetch.
Fixing workspace sample behavior with the "Create new" checkbox
Workspace creation from samples now correctly respects the "Create New" checkbox setting. Previously, creating a workspace from a sample always resulted in a new workspace, even when "Create New" was cleared. his behavior is fixed to allow the reuse of existing workspaces.
Handling SSH URLs in getting-started samples
An issue is resolved where custom getting-started samples configured with SSH Git URLs failed to clone the project. SSH-based repository URLs are now handled correctly, ensuring samples work as documented when you use SSH authentication. For more information, see Configuring getting started samples.
Reverting support for VS Code Composite Commands
Support for Composite Commands in Che Code is reverted because it could disrupt regular command execution under certain conditions. Reverting the support restores standard functionality until it can be appropriately implemented.