Release notes and known issues

OpenShift Dev Spaces runs on OpenShift 4.12–4.15 on the following CPU architectures:

For Red Hat OpenShift Dev Spaces 3.13, Red Hat will provide support for deployment, configuration, and use of the product.

There are some differences between Red Hat OpenShift Dev Spaces and the upstream project on which it is based, Eclipse Che:

Red Hat provides licensing and packaging to ensure enterprise-level support for OpenShift Dev Spaces.

With this release, you can easily choose an editor when starting a workspace from the User Dashboard by using the brand-new "Editor Selector" panel.

Find more details about specifying a custom editor in the official documentation.

Starting from this release, you can add parameters when defining a URL of a getting started sample:

     {
        "displayName": "Example",
        "description": "Example",
        "tags": ["example"],
        "url": "https://example.com/my-project.git?df=next/base/devfile.yaml"
      }

Find more details about configuring getting started samples in the official documentation.

With this release, you can specify which extensions are trusted and can access authentication tokens using the dedicated VSCODE_TRUSTED_EXTENSIONS environment variable defined in the devfile or ConfigMap:

   env:
     - name: VSCODE_TRUSTED_EXTENSIONS
       value: "<publisher1>.<extension1>,<publisher2>.<extension2>"

Find more details about the enhancement in the official documentation.

With this release, if the imagePuller option is enabled on the CheCluster Custom Resource level, the operator automatically fetches related images from both devfile and plugin registries to create and manage ImagePuller Custom Resource for faster workspace startup.

Find more details about the enhancement in the official documentation.

Before this release, only revoking GitHub OAuth from the User Dashboard was supported. Recently, GitLab added a Revoke a token API and it is now possible to also revoke the GitLab OAuth access right from the User Dashboard.

For other Git Services navigation to the provider website and following the instructions for revoking OAuth access is required.

Hovering over a workspace from the "Recent Workspaces" expands the name if it is long and does not fit the sidebar.

Starting from this release, when you create a Personal Access Token on the User Dashboard, the "Provider" field will correspond to the dedicated Git Service. Previously , oauth2- string with a random postfix was used. This resulted in poor visibility.

Previously, the persistUserHome CheCluster Custom Resource property was not working with the per-workspace storage strategy. The defect has been fixed in this release and now you can use the persistUserHome option with both the per-user and the per-workspace storage strategies.

Find more details about the property in the official documentation.

Before this release, there was a sporadic defect affecting workspace startup after using the "Restart Workspace from local Devfile" functionality from che-code. The following error message would appear: "You can only have 1 running workspace at a time". With this release, the issue is fixed.

Before this release, workspace startup from a Bitbucket Server private repository using OAuth2 failed with the "Repository/Devfile URL is missing" error. With this release, the issue is fixed.

Referencing an editor using che-editor URL parameter could result in a CORS-related network error. The defect has been fixed in this release.

Previously, when a developer created a Personal Access Token from the User Preferences, there was no validation of the Git URL. If the URL was invalid it led to login and dashboard usage issues due to a java.net.URISyntaxException: Illegal character exception. To resolve the access issue, you had to manually intervene with the generated secret. The defect has been fixed in this release.

Before this release, trailing spaces were not trimmed in the input field of the "Import from Git" widget resulting in the "URL or SSHLocation is not valid" error.

Previously, the Revoke OAuth button continued to be active after the execution. The defect has been fixed in this release.

With this release, devfile V1 is not supported anymore and the devfile-converter package is removed.

There is a known issue with Ansible Lightspeed and connection to the Ansible server. If the OpenShift Dev Spaces environment is not under *.openshiftapps.com domain, Ansible Lightspeed can not connect to the Ansible server.

There is no workaround available.

There’s a known issue with FIPS compliance that results in certain cryptographic modules not being FIPS-validated. Below is a list of requirements and limitations for using FIPS with OpenShift Dev Spaces:

Once the cluster is up and running, install OpenShift Dev Spaces 3.7.1 (3.7-264) and verify that the latest DevWorkspace operator bundle 0.21.2 (0.21-7) or newer is also installed and updated. See https://catalog.redhat.com/software/containers/devworkspace/devworkspace-operator-bundle/60ec9f48744684587e2186a3

The resulting binaries can be scanned and should pass without error.

As they are not related to cryptography, they do not affect FIPS compliance.

Currently, the debugger in Microsoft Visual Studio Code - Open Source does not work in the .NET sample.