Eclipse Che 7.110.0

Major Enhancements

Base developer image based on UBI10

The base developer image based on UBI10 is now available at quay.io/devfile/base-developer-image:ubi10-latest.

DevWorkspace Operator 0.37.0

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

SSH local to remote support in VS Code-based editors

Make it possible to connect to a DevWorkspace using the SSH protocol from a local (desktop) VS Code-based editor.

SSH.Local.to.Remote.mp4

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

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

Update Fabric8-Kubernetes-Client to version 7.4.0

With this release, the Fabric8 Kubernetes client used in che-server has been updated to version 7.4.0. For details on the changes included in this update, see the official release notes.

Bug Fixes

Provider name is empty for bitbucket.org

This release fixes a bug in the Add/Edit Personal Access Token (PAT) window and adds Bitbucket to the list of supported providers. Bitbucket SaaS OAuth 2 tokens are now automatically selected in the provider dropdown when editing a token.

The "Git repo URL" field on the "Create Workspace" page of the User Dashboard doesn't respect the private_token URL parameter

This release fixes a bug where the private_token URL parameter in the Git repo URL field on the Create Workspace page was ignored. Now, if you include private_token in the repo URL, the workspace will properly use it to authenticate.

.che/che-editor.yaml changes not applied on workspace restart — only on creation

Previously, changes in .che/che-editor.yaml were not applied when a workspace was restarted. This release fixes that bug, ensuring that custom editor updates defined in .che/che-editor.yaml are correctly applied after restarting the workspace.

Replace cluster's console URL with one to authentication credentials on landing page for Jetbrains Gateway-based workspaces

Reduce the number of login steps by displaying the user's authentication credentials for a cluster directly on the JetBrains Gateway landing page once the DevWorkspace has started.

Eclipse Che 7.109.0

Major Enhancements

CPU and Memory Limit widgets

With this release, the CPU and Memory Limit widgets on the Dashboard have been improved. You can now set CPU and memory limit values directly through input fields in the Advanced Options menu.

Create links in the entrypoint for files under /home/tooling/.config

Previously, with the UDI it was not possible to persist /home/tooling/.config files when spec.devEnvironments.persistUserHome is enabled in the CheCluster. With the latest UDI, /home/tooling/.config files will be persisted by creating a symlink from files under /home/tooling/.config to /home/user/.config in the entrypoint of the UDI.

Specify which files from /home/tooling/.config should be copied

When spec.devEnvironments.persistUserHome In some situations, it can be desirable to have files from /home/tooling/ copied to /home/user/ instead of creating a symlink. This can be useful for dotfiles or configurations, allowing users to edit and have their configurations stored in the persistent volume.

The latest UDI allows specifying which files should be copied via the .copy-files file:

FROM quay.io/devfile/base-developer-image:ubi9-latest
...
RUN echo ".my-config" >> /home/tooling/.copy-files
...

The example above creates in image where the /home/tooling/.my-config file is moved to the /home/user/.my-config in the container entrypoint, effectively copying the file into persistent storage after mounting.

Allow external TLS configuration for ingress/routes

This feature enables external tools such as cert-manager to inject TLS configuration into workspace ingresses/routes. The following fields have been added to the CheCluster CR:

spec:
  devEnvironments:
    networking:
      externalTLSConfig:
        // Enabled determines whether external TLS configuration is used.
        // If set to true, the operator will not set TLS config for ingress/route objects.
        // Instead, it ensures that any custom TLS configuration will not be reverted on synchronization.
        enabled: <bool>
        // Labels to be applied to ingress/route objects when external TLS is enabled.
        labels: <map[string]string>
        // Annotations to be applied to ingress/route objects when external TLS is enabled.
        annotations: <map[string]string>

Reduce number of ConfigMaps created in a user namespace

With this release the Che-managed ConfigMaps:

• che-editor-settings
• che-idle-settings
• che-proxy-settings

created in user namespaces have been combined into one ConfigMap named che-user-settings.

Add defaultContainerResources field to CheCluster

With this release, there is a new spec.devEnrinoments.defaultContainerResources introduced to the CheCluster CR which is used to update the config.workspace.defaultContainerResources field of the Che-owned DevWorkspaceOperatorConfig.

Example CheCluster CR:

spec:
  devEnrinoments:
    defaultContainerResources:
      limits:
        cpu: 200m
        memory: 200Mi
      requests:
        cpu: 100m
        memory: 100Mi

Specify the branch to use when starting a workspace from an SSH Git URL

This release adds the ability to specify a branch when launching a workspace from a Git repository using an SSH URL. This provides developers with greater control and flexibility when starting their development environments.

Multiple connections support in Jetbrains Gateway Plugin

Users can now view a list of multiple connection settings inside the JetBrains Gateway Plugin. The number of available servers can now also be limited.

UBI 10 support for Che Code

Previously the che-code editor failed to start with Red Hat Universial Base Image 10. With this release you can now explicitly reference those images in the components section of a devfile:

schemaVersion: 2.3.0
metadata:
  name: ubi10-minimal-demo
components:
  - name: tools
    container:
      image:  registry.access.redhat.com/ubi10-minimal@sha256:53de6ac7c3e830b0ddfc9867ff6a8092785bcf156ab4e63dfa9af83c880fd988
      args: ['tail', '-f', '/dev/null']
      endpoints:
        - exposure: public
          name: nodejs
          protocol: http
          targetPort: 3000
      memoryLimit: 2Gi
      memoryRequest: 256Mi
      mountSources: true
    attributes:
      controller.devfile.io/merge-contribution: true

Bug Fixes

Dashboard is blank when one of the DevWorkspace objects has an empty spec

This release fixes a bug that caused the User Dashboard to render a blank page when any DevWorkspace custom resource in the namespace had an empty spec. Now, even if a DevWorkspace object has an empty spec, the Dashboard will display correctly.

Dev Spaces personal access token UI does not allow URL parameter to contain port number

Previously, the User Dashboard did not support configuring a personal access token when the URL parameter included a port number. This limitation has been fixed in the current release, and personal access tokens can now be configured successfully with URLs that contain port numbers.

Ensure ca-certs-merged CM is resynced when disableWorkspaceCaBundleMount changed

Previously, the ca-certs-merged ConfigMap was not updated with the correct annotations when the spec.devEnvironments.trustedCerts.disableWorkspaceCaBundleMount field was set to true in the CheCluster CR.

Additionally when the certificates were mounted, the /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem file did not have sufficient permissions to run update-ca-trust.

With this release:

• The mounted tls-ca-bundle.pem file will now have 0444 permissions
• When the disableWorkspaceCaBundleMount field is set to true, the ca-certs-merged ConfigMap will have annotations required to mount to /public-certs.

More information about importing untrusted TLS certificates can be found in the official docs.

Eclipse Che 7.108.0

Major Enhancements

Documentation for Eclipse Open VSX On-Premises

With this release, official documentation is now available for running a private VS Code extension registry On-Premises. The guide provides end-to-end instructions on how to configure, build, deploy, and patch Eclipse Che to use your on-premises Open VSX instance.

JetBrains Rider (desktop)

JetBrains Rider IDE for .NET developers, and game development, is available in the "Editor Selector" of the workspace creation page.

JetBrains GoLand (desktop)

JetBrains GoLand IDE for Go developers is available in the "Editor Selector" of the workspace creation page.

JetBrains PhpStorm (desktop)

JetBrains PhpStorm IDE for PHP developers and related front-end technologies is available in the "Editor Selector" of the workspace creation page.

Add field to specify JetBrains IDE download URL

With this release, you can configure the JetBrains IDE download URL in the CheCluster custom resource by using the spec.devEnvironments.editorsDownloadUrls field.

apiVersion: org.eclipse.che/v2
kind: CheCluster
metadata:
  name: eclipse-che
  namespace: eclipse-che
spec:
  devEnvironments:
    editorsDownloadUrls:
      - editor: string
        url: string

This feature is useful in disconnected or air-gapped environments, where editors cannot be downloaded from the public internet.
Learn more about the editorsDownloadUrls property in the official documentation.

Better handling of the workspaces link, when using the link multiple times

This release gives you greater control when creating a new workspace using URL. Clicking a factory URL detects existing workspaces from the same Git repository, guiding you to an existing one or giving you the option to create a new workspace intentionally.

Key Updates

• Smart URL Handling: When you use a factory URL, Che checks for existing workspaces from that Git repository.
  • If a single workspace exists, it opens automatically, preventing an accidental duplicate.
  • If no workspace exists, a new one is created.
• Multi-Workspace Prompts: If a factory URL matches multiple existing workspaces, a warning message appears, prompting you to choose the specific one you want to open or to create a new workspace:

• Direct Workspace Targeting: You can bypass the multi-workspace prompt and open a specific instance directly by appending ?existing=<workspace-name> to the Git repository URL.

• Explicit Workspace Creation: You can force the creation of a new workspace by adding ?new parameter to a factory URL. This always creates a new workspace.

• Create New switch: On the Create Workspace page, the Create New switch gives you more control when using sample projects.

  • With the switch enabled (the default state), selecting a sample always creates a new workspace.
  • If you disable the switch, selecting a sample opens an existing workspace if one was previously created from that sample.

Learn more about the existing URL parameter in the official documentation.

DevWorkspace Operator 0.36.0

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

Bug Fixes

iss parameter is not excluded during workspace startup via factory URL

Previously, when starting a workspace from a factory URL, the iss (issuer) authentication parameter was not correctly excluded. This issue has been resolved, and the parameter is no longer visible in the URL at workspace start time.

Eclipse Che 7.107.0

Major Enhancements

Set the access mode for CDE PVCs in the CheCluster CR

With this release, you can set the access mode of Cloud Development Environment (CDE) persistent volume claims from the CheCluster custom resource:

apiVersion: org.eclipse.che/v2
kind: CheCluster
spec:
  devEnvironments:
    storage:
      perUserStrategyPvcConfig:
        storageAccessMode:
        - ReadWriteMany
      pvcStrategy: per-user

CDE persistent volume claims created after setting the storageAccessMode in the CheCluster CR will use the specified access mode.

Show editors for supported architectures only

You can hide editors that do not support the current system architecture on the User Dashboard.

Supported architectures are defined in each editor’s metadata:

schemaVersion: 2.3.0
metadata:
  name: che-code
  displayName: VS Code - Open Source
  description: Microsoft Visual Studio Code - Open Source IDE for Eclipse Che
  tags:
    - Tech-Preview
  attributes:
    arch:
      - x86_64
      - arm64
      - s390x
      - ppc64le

Support for copying /home/tooling/.config to /home/user/.config in the image entrypoint

Previously, when the spec.devEnvironments.persistUserHome feature was enabled and you started a Cloud Development Environment (CDE) for the first time using a UDI based image, the files in the /home/tooling/.config folder were not copied over to the /home/user/.config folder. With the latest update to quay.io/devfile/universal-developer-image:latest, the /home/tooling/.config folder will be copied over to /home/user/.config in the image entrypoint.

Update Traefik version to v3.4.0

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

Bug Fixes

GitLab for Non Standard Ports Fails

Before this release, GitLab OAuth integration did not work when GitLab was served on non-standard ports (i.e., other than 80 or 443). This issue has been resolved, and custom ports are now supported.

Always install release version of extensions

Before this release, Pre-Release versions of extensions were being installed in certain situations when installing the extensions specified in the recommendations section of the .vscode/extensions.json file. This issue has been resolved, and will now install the Release versions.

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.