Skip to content

Eclipse Che

Editors & IDEs

Platform for providing Kubernetes-based Cloud Development Environments for Enterprise Teams

TypeScript Latest 7.118.0 · 8d ago Security brief →

Features

  • Delivers full‑stack developer workspaces as containers on Kubernetes
  • Includes embedded web IDE, containerized runtimes, and project code
  • Supports collaborative, portable workspaces that run anywhere K8s is available

Recent releases

View all 15 releases →
Config change
7.118.0 Breaking risk
Auth

Prometheus auto‑setup, session warning, SSH handler, bug fixes

7.117.0 Breaking risk
⚠ Upgrade required
  • Azure DevOps OAuth2 flow will stop working after upgrade; migrate to OIDC configuration in che-server.
  • Deprecation warning: Azure DevOps standard OAuth2 authentication is deprecated and will be removed in a future release.
Breaking changes
  • Azure DevOps standard OAuth2 flow removed; OIDC authentication required via che-server component
  • Default branch browse URLs in Bitbucket Server no longer cause NullPointerException (behavior change)
  • Minimum Node.js runtime bumped to version 20.12 for che-server
Notable features
  • Browser‑based terminal start using ttyd
  • OpenShift namespace creation option via `spec.devEnvironments.createNamespaceDirectly: true`
  • Persistent user home directory enabled by default (`spec.devEnvironments.persistUserHome.enabled: true`)
Full changelog

Major Enhancements

Authenticate with Azure DevOps by using the OIDC flow

Azure DevOps is deprecating its standard OAuth2 authentication flow. Dev Spaces now supports the newer OIDC (OpenID Connect) authentication flow for Microsoft Azure DevOps, using Microsoft's authentication libraries in the che-server component. This change ensures continued compatibility with Azure DevOps for Git operations (clone, push, pull) and SCM authentication as Microsoft transitions away from the legacy OAuth2 flow.

Start a cloud development environment with a browser-based terminal

You can now start a cloud development environment with only a terminal in the browser:

The new editor definition uses ttyd (a command-line tool for sharing a terminal over the web) under the hood.

Use an external identity provider with OpenShift

Eclipse Che now supports running on OpenShift with an external OIDC provider enabled such as Keycloak. This feature was introduced in OpenShift Container Platform 4.20. For more details, see the official documentation.

Create Kubernetes namespaces instead of OpenShift projects

Before this release, Eclipse Che running on OpenShift created a project (project.openshift.io/v1) for each Che user. Starting from this release, the administrator can configure Che to create a Kubernetes namespace instead:

spec:
  devEnvironments:
    createNamespaceDirectly: true

Persistent user home directory is now enabled by default

With this release, persistent user home is enabled by default in the CheCluster CR:
spec.devEnvironments.persistUserHome.enabled

spec:
  devEnvironments:
    persistUserHome:
      enabled: true

With this feature, non-ephemeral workspaces automatically have a PVC mounted at /home/user.

For more details about persistent user home, see the official documentation.

Use a GitHub App for identity and authorization management

Eclipse Che now supports using a GitHub App (in addition to OAuth Apps) for managing identities and authorizations. GitHub App tokens use application permissions instead of token scopes, so token scope validation has been disabled accordingly.

Visual Studio Code - Open Source ("Code - OSS") updated to version 1.108.2

Visual Studio Code - Open Source ("Code - OSS") has been updated to the 1.108.2 upstream version. For more details, see the official release notes.

Restart workspaces from a local devfile in JetBrains IDEs

Users whose main editor is one of the JetBrains IDEs (over Gateway) can now edit their cluster devfile and apply the changes from the editor.

Bug Fixes

che-server metrics collection no longer fails after Micrometer upgrade

Reverted the Micrometer upgrade (1.11.5 to 1.16.1) that broke che-server metrics collection due to incompatible Prometheus integration package changes.

Bitbucket Server default branch browse URLs no longer cause a NullPointerException

Opening a workspace from a Bitbucket Server default branch browse URL (without the ?at= query parameter) no longer causes a NullPointerException in the URL parser.

Loader and status icon styles are now consistent on the User Dashboard

Loader and status icon colors now use PatternFly design tokens instead of hardcoded values. Dark theme status label colors are also corrected.

Multiple accessibility issues on the User Dashboard are now resolved

The following accessibility improvements are included in this release:

  • Keyboard navigation for editor selection, appearance settings, and provider dropdowns
  • Correct focus order and tab navigation on the User Preferences page
  • Improved color contrast for code editor line numbers and fold icons
  • Proper validation messages and required field indicators across Personal Access Token, SSH Keys, and Gitconfig forms
  • Distinct context for "Upload" buttons in the Add SSH Keys window
  • Private repository cloning now prompts for credentials instead of failing silently

Gateway plugin now connects to JetBrains 2026.1-based remote IDEs

Newer versions of JetBrains require a trusted path configuration to ensure a smooth project loading process.

Gateway plugin now connects to remote JetBrains IDEs without a project

The Gateway plugin can now connect to a developer workspace backed by a JetBrains editor with no project. The IDE welcome screen is displayed in such cases.

7.116.0 New feature
Notable features
  • Backup/restore mechanism for ${PROJECTS_ROOT} viewable in Dashboard Backups tab
  • SCC mismatch warning displayed on affected DevWorkspaces
  • Dashboard redesign using PatternFly 6 with updated components
Full changelog

Major Enhancements

Create a mechanism for backup/restore of ${PROJECTS_ROOT} from one cluster to another

If backups are configured for Eclipse Che, workspace backups can now be viewed from the Dashboard within the Backups tab.
Backups for existing and deleted workspaces are available for viewing. Workspace backups are used to recover uncommitted code changes for workspaces that have been deleted from the cluster.

Once a backup is determined, users can restore the workspace from the Dashboard.

More details about the backup and restore configuration can be found in the official documentation.

SCC Mismatch Warning for DevWorkspaces

The Dashboard now detects and warns when a DevWorkspace's Security Context Constraint (SCC) configuration doesn't match the current server settings. This typically occurs when container run capabilities are enabled after workspaces have already been created. Affected workspaces display a warning icon with a tooltip explaining the mismatch. Workspace startup is not blocked - users can still start the workspace, but are informed that it may fail due to the SCC configuration change.

Dashboard re-design with PatternFly 6

The User Dashboard has been migrated from PatternFly 5 to PatternFly 6. This includes updated Layout, Card, and Form components, replaced CSS variables and class names.

Add IPv6 Support to the User Dashboard

The Dashboard now fully supports single-stack IPv6 environments, such as OpenShift 4.20+ clusters. Previously, some URLs and API calls failed due to incorrect handling of IPv6 addresses.

Update Fabric8 Kubernetes Client to 7.6.1

The Fabric8 Kubernetes client dependency in Che Server has been updated to version 7.6.1, bringing in the latest bug fixes and improvements.

Add CAP_CHOWN to Container Run capabilities

For this release, the CHOWN Linux capability is added to the default security context for workspace containers when container run mode is enabled (alongside the existing SETGID and SETUID capabilities). This allows containers to change file ownership, which is needed for nested container scenarios.

Add editor support for remote development using JetBrains Toolbox App

Create an editor definition, "JetBrains Toolbox App (desktop)" that allows connecting a locally running JetBrains Toolbox App to a remove development workspace, over SSH.

Bug Fixes

MS Azure token validation in personal access tokens

Previously, adding a Microsoft Azure DevOps personal access token with invalid data (e.g., malformed token or organization name) would still save the token despite displaying an error. After a page refresh, the invalid token caused an "Illegal characters" error that blocked access to Eclipse Che. The token is now properly validated before saving, and invalid entries are rejected without affecting application access.

Use dynamic delimiter for advanced authorization values

Previously, there was a bug where usernames or group names containing commas would break the advanced authorization configuration since commas were hardcoded as the delimiter. Now Eclipse Che automatically picks a safe delimiter (from ,, |, ;, :, #, \t) that doesn't conflict with the usernames or group names.

7.115.0 Breaking risk
Notable features
  • Multicluster redirector spreads developer environments across multiple OpenShift clusters based on group membership
  • Global init containers configurable via `spec.devEnvironments.initContainers` in the CheCluster CR
Full changelog

Major Enhancements

Enterprise Scalability - Create a mechanism for spreading workspace load across multiple OpenShift clusters

You can now spread your developer environments across multiple OpenShift clusters using a new multicluster redirector. This service automatically redirects users to the correct Eclipse Che instance on the appropriate cluster based on their Red Hat OpenShift group membership. More details about the multicluster redirector solution for Red Hat OpenShift are available in the official documentation.

Provide initContainers field in the CheCluster CR

Global init containers can now be configured directly through the CheCluster custom resource from the spec.devEnvironments.initContainers field. The field accepts type []Container.

The new field can be configured as follows:

apiVersion: org.eclipse.che/v2
kind: CheCluster
spec:
  devEnvironments:
    initContainers:
      - name: my-container
        image: quay.io/my-container:latest

Setting the configuration above will add a my-container init container for all CDE pods.

Additionally, if the spec.devEnvironments.persistUserHome.enabled is set to true, the init-persistent-home init container can be overwritten by specifying an init container in spec.devEnvironments.initContainers named init-persistent-home.

Allow to globally configure the ssh_config for all dev spaces users

With this release, it is now possible to globally configure the SSH configuration for all Dev Spaces users. Administrators can extend the default SSH config file that is applied across the environment, and individual Che users can further extend this default configuration with their own custom SSH settings as needed. More details about mounting SSH configuration can be found in the official documentation.

Migrate devworkspace-generator to Yarn v4

With this release, the devworkspace-generator project has been migrated to Yarn v4. This update modernizes the dependency management setup, improves performance and consistency of installs, and aligns the project with the latest Yarn ecosystem improvements.

Migrate che-server typescript-dto module to Yarn v4

With this release, the che-server typescript-dto module has been migrated to Yarn v4. This change ensures a more up-to-date and maintainable build environment, providing improved dependency resolution and better alignment with current tooling standards.

Migrate chectl to Yarn v4

With this release, chectl has been migrated to Yarn v4 to align with the latest Yarn ecosystem improvements.

DevWorkspace Operator 0.40.0

DevWorkspace Operator 0.40.0 is now available, adding new functionality to Eclipse Che. For more information, see the changelog.

Document how to remove extensions from the Open VSX registry

With this release, the process for managing extensions in the Open VSX registry has been clarified with new documentation covering the supported and recommended approach for removing extensions. This includes guidance for scenarios where extensions may need to be removed manually, ensuring administrators have clear and consistent instructions for maintaining their registry.

Bug Fixes

Fix podman run command failure with parent devfiles

Resolved an issue where podman run coupled nested containers would fail in workspaces configured with parent devfiles. When spec.devEnvironments.disableContainerRunCapabilities is set to false, CDE containers receive HOST_USERS=false to indicate they're running in a dedicated user namespace, allowing container images to adjust their behaviour accordingly.

Add support for UBI 8-based images in the VS Code (desktop) (SSH) editor

Support samples whose development container are based on UBI 8 images when connecting a local instance of VS Code to that remote container over SSH.

Editor are not displayed on arm64 platform

With this release, an issue affecting the user dashboard on arm64 platforms has been resolved. Editors were not displayed because the system detected the architecture as aarch64, while the editor configuration defined the available architecture as arm64. The architecture handling has been aligned to ensure editors are correctly recognized and displayed on arm64 environments.

Potential startup failure in .NET 9 & Ansible samples with Jetbrains Desktop editors

Make Jetbrains Desktop editor images more resilient to running on UBI 9.7 based images, with any samples whose development container is based on a UBI < 9.7.

Che Code startup failure when developer container uses OpenSSL version < 3.4.0

Ensure Che Code (based on UBI 9.7) starts successfully when used in combination with a sample workspace whose developer container uses OpenSSL version < 3.4.0 (eg. UBI < 9.7).

Eclipse Che operator triggering unnecessary deployment rollouts

Previously, there was a bug where the ConfigMaps defined in the operator deployment changed order on every reconcile, causing
an endless reconcile loop. This issue has been fixed for this release.

Remove unnecessary entries that operator adds into Che ConfigMap

Previously, the Che ConfigMap contained obsolete fields which were used in the Che Server workspace engine. These fields have been removed for this release.

7.114.0 New feature
Notable features
  • Workspaces list includes an **Editor** column with icons and tooltips derived from `che.eclipse.org/che-editor` annotation
  • User Dashboard shows available Git branches in the **Git Repo Options** view when creating a workspace, reducing manual entry errors
  • Administrators can set maximum CPU/memory limits and requests for workspace containers via `spec.DevWorkspace.containerResourceCaps` in CheCluster CR
Full changelog

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.

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

About

Stars
7,162
Forks
1,218
Languages
TypeScript Shell JavaScript

Install & Platforms

Platforms
linux

Community & Support

Beta — feedback welcome: [email protected]