Eclipse Che 7.106.0

Major Enhancements

Update Visual Studio Code - Open Source ("Code - OSS") to 1.100.3 version

Visual Studio Code - Open Source ("Code - OSS") has been updated to the 1.100.3 upstream version. Read more in the official release notes.

Disable GitHub Copilot icon

With this release, the GitHub Copilot icon is disabled and not visible by default.

Note

The icon will be enabled back once Microsoft makes the GitHub Copilot extension fully opensource.

Documentation for running Eclipse Che at scale

Official documentation for running Eclipse Che at scale has been added in this release.

Prefer using files over environment variables for self-signed certificates

Starting from this release, the self-signed certificates are read from a file instead of the environment variable.

Update Maven to version 3.9.9 in the Universal Developer Image

With this release, Maven 3.9.9 is used in the default Universal Developer Image quay.io/devfile/universal-developer-image:ubi9-latest:

quarkus-api-example (main) $ mvn -v
Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
Maven home: /home/tooling/.sdkman/candidates/maven/current
Java version: 17.0.13, vendor: Eclipse Adoptium, runtime: /home/tooling/.sdkman/candidates/java/17.0.13-tem
Default locale: en, platform encoding: UTF-8
OS name: "linux", version: "5.14.0-427.70.1.el9_4.x86_64", arch: "amd64", family: "unix"

DevWorkspace Operator 0.35.1

The DevWorkspace Operator 0.35.1 has been released, providing new functionality to Eclipse Che. View the changelog here.

Bug Fixes

Authorization icon is disabled when OAuth token is set on Bitbucket.org

Previously, the icon authorization was incorrectly disabled when the OAuth token was set on Bitbucket.org.

The defect has been fixed in this release.

Error redirect page when accepting OAuth2 factory on Bitbucket server

Before this release, there was a defect resulting in an error redirect page when accepting the OAuth2 factory on Bitbucket server.

Dashboard CDE list should be opened after login if it has a workspace created

Previously, the "Create Workspaces" page was opened instead of the "Workspaces" on the User Dashboard if at least one Cloud Development Environment (CDE) existed. The defect has been fixed in this release.

Eclipse Che 7.105.0

Major Enhancements

Allow operator to run in namespaces with enforce=restricted Pod Security Standards

Starting from this release, you can have both the operator and operands running in namespaces with the
pod-security.kubernetes.io/enforce=restricted labels. Learn more about enforcing Pod Security Standards with Namespace Labels from the official Kubernetes documentation.

Allow to specify persistent volume type RWX when using strategy per-user

With DevWorkspace Operator 0.35.0, you can configure the storage access mode for PVCs managed by the DevWorkspace Operator.

apiVersion: controller.devfile.io/v1alpha1
kind: DevWorkspaceOperatorConfig
metadata:
  name: devworkspace-operator-config
  namespace: $OPERATOR_INSTALL_NAMESPACE
config:
  workspace:
    storageAccessMode:
    - ReadWriteMany

With the configuration above, newly created PVCs will have the ReadWriteMany access mode:

Enable Che Server Build Support on s390x Architecture

The che-server component is now built on the s390x architecture, ensuring successful builds on IBM Z running RHEL 9.4 in the upstream.

Bug Fixes

Common PVC cleanup job can be assigned to incorrect node in multi-node cluster

With DevWorkspace Operator 0.35.0, if there are multiple Cloud Developer Environments (CDEs) using a common PVC, and if a running CDE is deleted, the cleanup job pod will always be scheduled on the node the CDE pod was running in. For common PVCs with the ReadWriteOnce access mode, this prevents the Multi-Attach error which caused the cleanup job to be assigned to an incorrect node .

Do not overwrite NODE_EXTRA_CA_CERTS environment variable on the workspace startup

You can use your own CA certificate by specifying the path to the certificate in the NODE_EXTRA_CA_CERTS environment variable. This fix guarantees that the value of the NODE_EXTRA_CA_CERTS environment variable will not be overwritten on the workspace startup.

Non-admin user can't fetch list of workspaces into JetBrains Gateway using Plugin

Previously, if a user was not allowed to list the 'devWorkspace' objects in one of the namespaces, this led to an empty workspace list in the Gateway UI. The defect has been fixed in the v0.0.11 plugin release.

ConfigMap vscode-editor-configurations does not replicate the changes in the namespace

Previously, changes added to the settings.json and extensions.json in the vscode-editor-configurations CM were not applied correctly. The defect has been fixed in this release. Learn more about applying editor configurations in the official documentation.

VS Code OpenShift Toolkit extension does not detect connection on the cluster it is deployed on

Before this release, OpenShift Toolkit extension did not detect a connection on the cluster it is deployed on. The defect has been fixed in this release, and now the connection is displayed correctly:

Token injection fails on workspace restart after expiry

Previously, if the OpenShift user token expired, restarting the workspace did not inject/refresh the new token. The defect has been fixed in this release.

User Dashboard showed wrong devfile content of workspace created from private GitHub repo using SSH URL

Before this release, the wrong devfile content was displayed for workspaces created from a private GitHub repository using SSH URL. The defect has been fixed in this release.

Eclipse Che 7.104.0

Major Enhancements

Support for JetBrains Gateway 2025

With this release, JetBrains Gateway 2025 is supported by the dedicated plugin, which is compatible with Eclipse Che.

Allow filtering samples by tags and languages on the User Dashboard

With this release, you can filter samples on the User Dashboard by both tags and languages.

Use UDI 9 as the default development image

With this release, quay.io/devfile/universal-developer-image:ubi9-latest is used as the default development image. To override it, use the spec.devEnvironments.defaultComponents Custom Resource property:

spec:
  devEnvironments:
    defaultComponents:
       - name: universal-developer-image
         container:
           image: <>

Add NodeJS MongoDB sample in Eclipse Che website

A new Node.js MongoDB sample that has been contributed to devfile.io is available on the Eclipse Che official website with this release.

Resource requirements for running a CDE with a JetBrains IDE

Information about additional memory and CPU requirements for a JetBrains IDE (e.g. IntelliJ IDEA Ultimate) is available in the official documentation.

Bug Fixes

Workspaces which used ubi9-based samples as tool containers failed to start with JetBrains IntelliJ IDEA (desktop)

Before this release, there was a known issue with starting Cloud Development Environments (CDEs) created with ubi9-based images (ubi9-minimal, ubi-init, and ubi9) in the desktop version of JetBrains IntelliJ IDEA. The IDE did not load, causing the start of the workspace to fail after some time. The defect has been fixed in this release.

Git history wiped out after workspace pod crash

Previously, there was a defect related to the loss of all Git history if a workspace pod was restarted with a default devfile when the persistent storage strategy specified in the CheCluster was per-workspace. The defect has been fixed in this release.

Setting controller.devfile.io/storage-type attribute to ephemeral in devfile doesn't use ephemeral storage

The regression related to the controller.devfile.io/storage-type: ephemeral attribute has been fixed in this release, and Cloud Development Environments (CDEs) created from devfiles with this attribute now correctly use the emptyDir volumes.

Error redirect page when accepting OAuth2 factory on Bitbucket server

Previously, when accepting Bitbucket server's OAuth2 prompt, there was an unexpected error redirect page with the error stack trace: {"message":"Cannot invoke \"String.length()\" because \"this.input\" is null","trace"}. The defect has been fixed in this release.

Gitlab raw devfile url is not recognized

Previously, Gitlab raw devfile URLs were not correctly processed, resulting in the default devfile being used for Cloud Development Environment (CDE) startup. The defect has been fixed in this release.

Gitlab repository URL with multiple groups and subgroups is corrupted

Previously, when you launched a workspace from the Dashboard using a Gitlab repository URL with multiple groups and subgroups, it failed when a branch from the Git Repo Options was also provided from the Dashboard. The defect has been fixed in this release.

Bitbucket SSH URL to create workspace not working

Before this release, you could not create a Cloud Development Dnvironment (CDE) based on Bitbucket SSH URLs because the startup was interrupted by the Warning alert:Failed to create the workspace error. The defect has been fixed in this release.

Post start events execute in alphabetic order rather than listed sequence, leading to potential confusion

Previously, postStart commands were executed based on alphabetical order rather than the sequence in which they were listed in the devfile, leading to potential confusion, especially when a specific execution order is expected based on the listed sequence. Starting from this release, the execution happens in sequential order in the way the commands are listed in the postStart section of a devfile:

postStart:
  - command-one
  - command-two
  - command-three

Pre-release versions of the extensions are installed by default from https://open-vsx.org

Previously, the pre-release versions of the extensions were installed by default from https://open-vsx.org. The defect has been fixed in this release, and now the stable versions of the extensions are installed by default.

Eclipse Che 7.103.0

Major Enhancements

DevWorkspace Operator resource pruner

Starting from DevWorkspace Operator version 0.34.0, you can configure a pruner that automatically cleans up DevWorkspace objects that were not in use for a certain period of time. To set the pruner up, configure the DevWorkspaceOperatorConfig object as follows:

apiVersion: controller.devfile.io/v1alpha1
kind: DevWorkspaceOperatorConfig
metadata:
  name: devworkspace-operator-config
  namespace: crw
config:
  workspace:
    cleanupCronJob:
      enabled: true
      dryRun: false
      retainTime: 2592000 # By default, if a workspace was not started for more than 30 days it will be marked for deletion
      schedule: “0 0 1 * *” # By default, the pruner will run once per month

You can find more details about DevWorkspace Operator Configuration in the official documentation.

Improve handling of auto-mount path collisions

Handling of the auto-mount path collisions has been improved in the latest DevWorkspace Operator version. When two automount configmaps or secrets share the same mount path with controller.devfile.io/mount-as: subpath, an error message will appear when trying to start a DevWorkspace.

Eclipse Che 7.102.0

Major Enhancements

Provide the ability to disable "Install from VSIX..." functionality in VS Code IDE

Previously, users could manually download and install unapproved Visual Studio Code extensions in the .vsix format. This could lead to the installation of potentially unapproved and malicious extensions.
With this release, admins can use the ConfigMap to disable the Install from VSIX…​ feature and prevent the download and installation of unapproved extensions.

Learn more about the procedure in the official documentation.

Hide deprecated IntelliJ IDEA Community edition from the dashboard by default

By default, the deprecated Projector-based IntelliJ IDEA Community edition is hidden on the User Dashboard from this release on, and will be completely removed in future releases. To enable the deprecated editor on the User Dashboard in the current version, use the dedicated environment variable CHE_SHOW_DEPRECATED_EDITORS in the Custom Resource:

spec:
  components:
    dashboard:
      deployment:
        containers:
        - env:
          - name: CHE_SHOW_DEPRECATED_EDITORS
            value: true

Allow hiding editors on the User Dashboard

Starting from this release, the admin can hide particular editors on the User Dashboard using the dedicated environment variable CHE_HIDE_EDITORS_BY_ID in the Custom Resource :

spec:
  components:
    dashboard:
      deployment:
        containers:
        - env:
          - name: CHE_HIDE_EDITORS_BY_ID
            value: che-incubator/che-webstorm-server/latest, che-incubator/che-webstorm-server/next,
                   che-incubator/che-rubymine-server/latest, che-incubator/che-rubymine-server/next,
                   che-incubator/che-pycharm-server/latest, che-incubator/che-pycharm-server/next,
                   che-incubator/che-clion-server/latest, che-incubator/che-clion-server/next,
                   che-incubator/che-idea-server/latest, che-incubator/che-idea-server/next,
                   che-incubator/che-idea/latest, che-incubator/che-idea/next

Allow to provide filter as url parameter on Dashboard

With this release, it is possible to add an optional filter URL parameter on the "Create Workspace" page of the User Dashboard, and display only a portion of samples based on a particular technology e.g. Quarkus dashboard/#/create-workspace?filter=quarkus

Support creating CDEs by pointing directly to a devfile.yaml on GitHub

Starting from this release, you can create a Cloud DeveloperEnvironment (CDE) by using a GitHub repository URL of a directory with a devfile, or a GitHub repository URL directly pointing to the devfile. Previously, you could only use URLs of the GitHub repository, branch, and tag, as well as RAW devfile URLs to create a CDE.

Important

The name of the devfile must be devfile.yaml or .devfile.yaml.

Update traefik version to v3.3.5

Traefik version used by the operator has been updated to the v.3.3.5 version. More details about the new version are available in the official release notes.

Contribute Node.js MongoDB sample to devfile.io

A new Node.js MongoDB sample has been contributed to devfile.io.

Installing che-operator with helm

Official documentation for updating Eclipse Che helmcharts, together with detailed steps for installation of cert-manager and DevWorkspace Operator is available in this release.

Bug Fixes

Workspace is not deleted when another workspace is running in the same user namespace

Previously, when you deleted a workspace while using the per-user PVC strategy, the workspace might not have been deleted correctly if another workspace was running.
In this release, a warning message will appear in such situations with a suggestion to stop running workspaces before you delete any.

Personal Access Token authentication failing after Bitbucket server was upgraded to 8.19.14

The defect related to Personal Access Token (PAT) authentication failures on Bitbucket server 8.19.14 has been fixed in this release.

Bitbucket Server OAuth2 does not work with access-tokens that include special characters

Previously, using OAuth2 with a Bitbucket server could fail if the username had special characters.
The defect has been fixed in this release, and all the special characters are properly decoded.

"Error: invalid_request. Invalid redirect URI." error when connecting to Ansible Lightspeed from Ansible extension

Previously, there was a defect related to the connection to the Lightspeed service when you used the Ansible extension. Following error message would appear: "Error: invalid_request. Invalid redirect URI." This defect has been fixed in this release.

chectl cannot be installed on Apple Silicon

Previously, it was not possible to install the chectl CLI on the Apple Silicon MacBook. The defect has been fixed in this release, and the arm64 architecture is officially supported for the CLI.

Unable to access workspace in VS Code Desktop if the name is longer than 20 characters

Previously, if a workspace name was longer than 20 characters, the Visual Studio Code desktop flow was broken. The defect has been fixed in this release.

Eclipse Che 7.101.0

Major Enhancements

Allow to configure product.json for Visual Studio Code - Open Source using ConfigMap

With this release, you can configure not only settings.json and extensions.json, but also product.json for Visual Studio Code - Open Source editor by using a dedicated ConfigMap:

apiVersion: v1
kind: ConfigMap
metadata:
  name: vscode-editor-configurations
data:
  extensions.json: |
    {
      "recommendations": [
          "dbaeumer.vscode-eslint",
          "github.vscode-pull-request-github"
      ]
    }
  settings.json: |
    {
      "window.header": "A HEADER MESSAGE",
      "window.commandCenter": false,
      "workbench.colorCustomizations": {
        "titleBar.activeBackground": "#CCA700",
        "titleBar.activeForeground": "#ffffff"
      }
    }
  product.json: |
    {
      "extensionEnabledApiProposals": {
        "ms-python.python": [
          "contribEditorContentMenu",
          "quickPickSortByLabel",
        ]
      },
      "trustedExtensionAuthAccess": [
        "<publisher1>.<extension1>",
        "<publisher2>.<extension2>"
      ]
    }
immutable: false

Learn more about the procedure in the official documentation

Improve mounting certs into users containers

The process of mounting certificates into user's containers has been improved in this release:

• The obsolete che-trusted-ca-certs ConfigMap that was used for mounting certificates into the /public-certs directory was removed.
• The ca-certs-merged ConfigMap is now created in the user namespace and is merged either into the /public-certs directory or /etc/pki/ca-trust/extracted/pem, depending on the value of spec.devEnvironments.trustedCerts.disableWorkspaceCaBundleMount defined in the CR.

More details about importing untrusted TLS certificates are available in the official documentation.

Develocity integration

Starting from this release, the che-server builds are revved up by Develocity, which enhances developer productivity through features such as Build Scan for build insights and collaborative troubleshooting, and remote Build Cache for build acceleration. Develocity also provides comprehensive reporting and visualization of build data.

To view the Build Scan produced by a build, click on the generated link at the end of the build. Build Scans are available locally and on GitHub Action CI (limited to users authenticated to publish local scans). You can access all scans published by the che-server builds on the Eclipse Develocity dashboard by searching for the che server project.

Here are additional useful links with the che-server builds data:

• Build Scans
• Trends dashboard
• Failures dashboard
• Failed and flaky Tests dashboard

Update to Fabric8-Kubernetes-Client 7.1.0

Fabric8 Kubernetes Client used in the che-server component has been updated to the latest 7.1.0 version. More details about the new version are available in the official release notes.

Bug Fixes

OpenShift image is broken on the User Dashboard

The broken link for the OpenShift console image on the User Dashboard has been fixed in this release.

Setting disableWorkspaceCaBundleMount: true doesn't stop mounting certificates into /etc/pki/ca-trust/extracted/pem/ dir

Previously, setting disableWorkspaceCaBundleMount: true property in the CR did not stop mounting certificates into /etc/pki/ca-trust/extracted/pem/ directory. The defect has been fixed in this release.

No space left on device when build che-code image

The defect related to the building of the che-code image from CDE has been fixed in this release.

Eclipse Che 7.100.0

Major Enhancements

Microsoft Azure DevOps Server (TFS) support

Starting from this release, you can configure a Personal Access Token (PAT) for accessing a Microsoft Azure DevOps Server (TFS) instance hosted on-premise.

Note

OAuth 2.0 is not currently supported on the Azure DevOps Server.

Learn more about the PAT setup in the official documentation.

Simplify importing untrusted TLS certificates

The procedure for importing untrusted TLS certificates has been sufficiently simplified in this release.
You can learn more about the procedure in the official documentation.

Bug Fixes

Cannot activate the 'Python Debugger' extension because its dependency 'Python' failed to activate

Previously, there was an issue where 'ms-python.python' extensions failed to be activated when the Visual Studio Code - Open Source ("Code - OSS") editor was refreshed in the browser. This defect was fixed in this release.

POST ​/kubernetes​/namespace​/provision could take up to 30 seconds on some clusters, resulting in broken dashboard

When you access the User Dashboard, it makes a POST /Kubernetes/namespace/provision request. In some clusters, the request could take more than the 15-second timeout, making it impossible to access the user dashboard. The timeout was updated to 30 seconds in this release. Additionally, it is now possible to customize the timeout using the CHE_DASHBOARD_AXIOS_REQUEST_TIMEOUT environment variable.

Dashboard should serve getting-started devfile samples from /index/all

Previously, the User Dashboard served the getting started samples from the /index route of the configured externalDevfileRegistries. Starting from this release, the /index/all route is used instead.

Do not fetch git username and email if the gitconfig configmap contains the data

Previously, Eclipse Che would fetch the git username and email from the git provider regardless of whether the data already existed in the workspace-userdata-gitconfig-configmap ConfigMap in the user's namespace. In this release, the ConfigMap is checked beforehand, and fetches the data from the git provider only if needed.

Gitlab API is requested for non-Gitlab PATs

Before this release, there was an unwanted GitLab API validation request if any Personal Access Token (PAT) existed in your namespace.

2025-03-06 08:08:33,265[nio-8080-exec-1]  [TRACE] [o.e.c.a.f.s.g.GitlabApiClient 78]    - executeRequest=https://gitlab.com/api/v4/user GET`. The defect has been fixed in this release.

The request has been removed in this release.

The http raw devfile is not properly resolved by the User Dashboard

This release fixes a bug where the User Dashboard did not properly display the original devfile in the workspace's 'Devfile' view

A workspace with a devfile that uses a parent devfile failed to start due to the error: 'Cannot add property attributes, object is not extensible'.

Before this release, workspaces based on devfiles with parent reference failed to start with the following error message: "Cannot add property attributes, object is not extensible". The defect has been fixed in this release.

Automatically restart from local devfile when devfile failed to be resolved at startup

A regression related to the automatic restart from the local devfile for SSH URLs has been fixed in this release.

Start workspace from Gitea SSH URL is interrupted by a warning page

Previously, workspace startup from a Gitea repository using SSH URL was interrupted by the following warning message: "Cannot read properties of undefined (reading schemaVersion). The defect has been fixed in this release.

Git user.name and user.email on Gitconfig page are not displayed if the page is opened before PAT or OAuth configuration

Before this release, if you opened 'Gitconfig' tab from the User Dashboard before creating a Personal Access Token (PAT) or setting up OAuth, the user's name and email were not displayed. The defect was fixed in this release.

Eclipse Che 7.99.0

Major Enhancements

Microsoft Visual Studio Code desktop flow

Starting from this release, you can connect a local desktop Microsoft Visual Studio Code instance to a Cloud Development Environment (CDE) using the Remote - Tunnels extension:

Learn more about the setup in the official documentation.

Documentation

Platform-specific installation guides for the DevWorkspace Operator

Eclipse Che is using the DevWorkspace Operator under the hood to manage the lifecycle of the Cloud Development Environments. In this release, Platform-Specific Installation Guides for kind, minikube, and OpenShift have been added to the project's documentation.

Bug Fixes

Obsolete Visual Studio Code editor version is used in the existing workspaces after version upgrade

Previously, there was a known issue affecting Visual Studio Code - Open Source ("CODE - OSS"). After an upgrade, an obsolete version of the editor continued being used for existing workspaces instead of the new version. The defect has been fixed in this release.

A new workspace can not be created if the target devfile contains both parent reference and the storage-type attribute

Before this release, you could not create a workspace if the target devfile had a parent reference, and had the storage-type field overridden, since the parent schema does not support overrides in the attributes. The defect has been fixed.
Starting from this release, the attributes.controller.devfile.io/storage-type is not applied in the child devfile if it is defined in the parent. The Change Storage Type widget is also disabled in this situation:

Broken 'Devfile Viewer' styles on the User Dashboard

Before this release, the 'Devfile Viewer' styles were broken on the User Dashboard for some devfiles:

The defect has been fixed in this release.

The 'Changes' commands in the drop-down list are not available on the 'Source Control' panel

Before this release, the 'Changes' commands in the drop-down list were not available on the 'Source Control' panel of the Visual Studio Code - Open Source ("CODE - OSS"):

The defect has been fixed in this release.

Failed to create workspace when launching private repository factory with refused OAuth

The defect related to the workspace startup from a private repository when OAuth was refused has been fixed in this release.

Start workspace page displays misleading warning when opening gogs public repository using HTTP URL

Previously, a warning message "The Bitbucket integration is not configured properly" appeared when opening gogs public repository using HTTP URL

The defect has been fixed in this release.

Warning message "Cannot build a factory with any of the provided parameters" appears when creating workspace from a gogs private repository using an SSH URL

Previously, a warning message "Cannot build a factory with any of the provided parameters" appeared when creating a workspace from a gogs private repository using an SSH URL. The defect has been fixed in this release.

Eclipse Che 7.98.0

Major Enhancements

Mount proxy environment variables to dashboard container

With this release, if there is a proxy configured in the cluster, the proxy configuration is mounted to the che-dashboard container as environment variables: HTTP_PROXY, HTTPS_PROXY, NO_PROXY.

Reduce dashboard frontend bundle size

The dashboard frontend bundle size has been decreased by 14 percent in this release.

Before

After

Bug Fixes

Cannot create workspace using factory from Azure DevOps repositories if OAuth is configured

Previously, there was an issue that made creating workspaces from the dashboard factory flow from Azure DevOps repositories (private and public) impossible if OAuth was configured. This defect has been fixed in this release.

Eclipse Che 7.97.0

Major Enhancements

Allow to configure securityContext for the gateway container

You can set up the securityContext for the CDE pods in the CheCluster CR:

spec:
  devEnvironments:
    security:
      containerSecurityContext:
        allowPrivilegeEscalation: false
        capabilities:
          drop:
            - ALL
      podSecurityContext:
        seccompProfile:
          type: RuntimeDefault

With this release, the securityContext is also applied to the CDE's che-gateway container.

Add the ncat utility to the project clone image

With this release, the ncat utility has been added to the project-clone container of the CDE.

$ podman run --rm quay.io/devfile/project-clone:v0.32.1 nc --version
Ncat: Version 7.92 ( https://nmap.org/ncat )

Create a common entrypoint for base and UDI, fix .config ownership for Podman 5 support

With this release, a common entrypoint.sh script is used for both the base-developer-image and the universal-developer-image (UDI), making the behaviour between the two images consistent.

The base-developer-image and UDI are updated so that the storage driver for Podman (fuseoverlay-fs or vfs) is determined automatically in the entrypoint. As a result, if the /dev/fuse device is available in the CDE, the entrypoint will configure the ~/.config/containers/storage.conf file automatically to use fuse-overlayfs.

Additionally, the ownership of the ~/.config folder is set to the current user, which is a requirement for Podman 5.x.

Bug Fixes

ServiceAccount token cached incorrectly on the User Dashboard

Previously, ServiceAccount token located at the path /var/run/secrets/kubernetes.io/serviceaccount/token was cached on the User Dashboard end and was not refreshed properly. The defect has been fixed in this release.

Automatically restart from local devfile when devfile failed to be resolved at startup for SSH URLs

Regression related to the automatic restart from the local devfile for SSH URLs has been fixed in this release.

Kubeconfig format corruption after switching clusters and restarting workspace

Kubeconfig format corruption after switching clusters and restarting CDE has been fixed in this release.

Restart from local devfile doesn't work anymore

Previously, Che Code's Restart Workspace from Local Devfile functionality was not working when attributes in the DevWorkspace CR had null values. This defect has been fixed in this release.

Can not create a workspace using SSH

Previously, there was a Cannot add property controller.devfile.io/bootstrap-devworkspace, object is not extensible error when you tried to create a workspace with an SSH URL from the Che dashboard. This defect has been fixed in this release.

Current stow implementation in udi8/9 breaks under certain conditions

Previously if devEnvironments.persistUserHome.enabled and devEnvironments.persistUserHome.disableInitContainer were both true, and if there was a file in the /home/user directory that would cause a stow conflict, the stow command would still run and fail due to the conflict. With this release, UBI and UDI entrypoint automatically add conflicting files into the /home/tooling/.stow-local-ignore to prevent the stow failure.

Use current project directory at terminal creation

When creating new terminals in the Visual Studio Code - Open Source ("Code - OSS") editor with the New Terminal (Select a Container) option, the initial directory was not the current project directory (ex. /projects/<project-name>). This defect has been fixed in this release.

Documentation

Documentation for applying editor configurations from a ConfigMap

With this release it is now possible to apply Che Code settings.json and extensions.json to your Visual Studio Code - Open Source ("Code - OSS") editors using a ConfigMap. Learn more in the official documentation.