Major Enhancements
Airgap support for VS Code as an Eclipse Che editor
It's now possible to run an Eclipse Che workspace using VS Code as editor in a cluster with a restricted/disconnected network (air gap). Eclipse Che is now able to run a local open-vsx registry instance within the plugin-registry pod so that VS Code editors running in workspaces can use it to manage extensions. To control what instance of open-vsx should be used in the workspaces we have introduced a new field inCheCluster CR to specify the open-vsx URL.
Avoid automatic creation of users namespaces through a configuration option
A new field in CheCluster has been added to avoid that users namespaces get created automatically. If devEnvironments.defaultNamespace.autoProvision is set to false and a user doesn't have a Che namespace, workspace creation will fail. autoProvision is set to true by default.
When starting a workspace with the same name as an existing one ask users if they wants to replace the pre-existing one
Previously, when starting a workspace with the same name of an existing one, Che would return an error and users should either manually delete the existing one or rename the new workspace. Now users are asked if they want to re-open the existing one or if they want to replace it with the new workspace.
Allow to configure git services in Che configuration
Configuring Git services OAuth will be more straightforward for administrators as it's possible to reference Git servies secrets from CheCluster CRs. On OpenShift those new configuration will be available from the OpenShift Console UI.
Faster workspace startup as a result of avoiding changes to DevWorkspace CR after it has started
The startup times of workspaces that have a persistent volume attached (the default) has been significantly improved.
Support OAuth flow for GitHub Enterprise Server
Administrators can now configure Che instances to automatically connect to GitHub Enteprise Server to retrieve and configure users personal access tokens. Note the GitHub Enterprise Cloud was already supported.
Allow to configure workspaces persistent storage from Eclipse Che CR
Workspaces persistent storage options like the strategy and the size are now configurable using CheCluster CR. It's also possible to set the storage strategy to per-workspace now so that developers will be able to run multiple workspaces concurrently.
Major Bug Fixes
Files in .vscode and .che folders of a git repository are ignored at workspace creation
Files in .vscode and .che subfolders need to be processed during workspace creation as they can contain important workspace details (as the editor and the che-theia plugins to pre-install) but were ignored in recent versions due to a regression. This has been fixed in this release.