Skip to content

Eclipse Che 7.78.0
Compare
Choose a tag to compare
@l0rd l0rd released this 04 Jan 16:23
· 95 commits to main since this release
7.78.0
d1d0991

Major Enhancements

Add a way to reject the authorization opt-out flag from the dashboard

Starting from this release a user can revoke the authorization for configured Git Services from the User Dashboard:

revoke_auth

Add support for PATs in GitHub Enterprise Server

Personal Access Token (PAT) for the GitHub Enterprise Server (self-hosted instance) can be now configured from the User Dashboard. Before this release, only GitHub.com and GitHub Enterprise Cloud were supported.

Improve options when workspace startup fails

In this release, a few major enhancements have been made for cases when a workspace fails to start for some reason:

Workspace startup page

A user can navigate to the OpenShift cluster and edit the DevWorkspace spec right from the workspace startup screen:

Screenshot 2023-11-23 at 17 03 10

Workspaces list page

On the 'Workspaces' page the problematic workspace will be marked with the warning sign:

Screenshot 2023-11-23 at 17 03 23

Workspace details page

it is now possible to navigate to the DevWorkspace object from the 'Overview' tab of the User Dashboard when running on OpenShift:

Screenshot 2024-01-04 at 17 16 36

Support devfile private raw URLs with ?token parameter on github.com

The ?token URL parameter is now supported for resolving private devfiles from github.com e.g. raw.githubusercontent.com/account/repository/main/devfile.yaml?token=<token>.

Set Java 17 as the default in the Universal Developer Image

Java 17 is now used by default in the Universal Developer Image:

Screenshot 2024-01-04 at 14 21 25

Major Bug Fixes

Issue accessing existing workspaces which shows "No PersonalAccessTokenFetcher configured" error

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.

VS Code che-resource-monitor extension not working

To get the metrics, the resource monitor extension needs to know the pod name provided by the HOSTNAME environment variable.
However, sometimes the variable could be overridden with a different value which breaks the plugin. To avoid this problem it has been decided to copy the HOSTNAME env var to DEVWORKSPACE_POD_NAME env var before launching the editor and fall back on the new variable when necessary.

Assets 2
Loading