Release notes and known issues

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

For Red Hat OpenShift Dev Spaces 3.10, 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 use GitHub Device Authentication in Microsoft Visual Studio Code - Open Source to activate extensions. For more information about this feature, check GitHub device activation flow.

The GitHub Copilot extension can now be activated using GitHub Device Authentication. To activate it, follow these steps:

With this release, you can configure the OAuth flow for GitHub Enterprise Server and GitHub SaaS simultaneously. More details about this feature can be found in this demo video.

With this release, routes generated for the Microsoft Visual Studio Code - Open Source editor use HTTPS protocol by default.

With this release, you can use the User Dashboard to configure the user name and email that will be used in the workspace '.gitconfig' settings.

Before this release, backend issues resulted in a generic "Backend is not available" error message displayed on the User Dashboard. With this update, the error includes the HTTP error code and the affected endpoint.

With this release, when you stop a workspace from the Microsoft Visual Studio Code - Open Source editor, you are automatically redirected to the User Dashboard.

With this release, if you reject an SCM provider authorization request while creating or starting an existing workspace, your choice is saved in the workspace-preferences config-map in the namespace. During the subsequent workspaces startups, the prompt to proceed with the OAuth authorization for the rejected SCM provider no longer appears.

With this release, you can specify preStop events in the devfile that will be executed before stopping the workspace. Similar to postStart, multiple devfile commands can be specified as preStop:

    events:
      preStop:
        - first-command
        - second-command
        - third-command

    events:
      preStop:
        - first-command
        - second-command
        - third-command

With this release, you can configure your SSH key from the User Dashboard.

Before this update, enabling the persistence of the home directory broke the Universal Developer image home directory, PATH, and environment variables. With this update, this issue is fixed.

Before this update, re-opening an existing workspace resulted in a "No PersonalAccessTokenFetcher configured" error message. With this update, the token is refreshed on a workspace restart.

Before this update, rejecting SCM authorization led to an error appearing at workspace start. With this update, the workspace starts correctly.

Before this update, an "Unauthorized" error message would occasionally appear at the 'Open IDE" phase of the workspace start. With this update, the issue is fixed.

Before this update, the "Bearer Token Authorization" error would occasionally appear in the dashboard. With this update, retry request implementation solves the issue.

Before this update, it was not possible to start a workspace based on the Microsoft Azure DevOps Git repositories with white space characters in the URL. With this update, the issue is fixed.

Before this update, builds would fail because of missing common tooling config directories. With this update, the following directories are pre-created in the default UDI with the correct permissions allowing users to write into them from the workspace:

There is a known issue where automatic installation of the recommended Microsoft Visual Studio Code - Open Source extensions fails if you’re using a Java or Ansible sample.

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.