github eclipse-che/che 7.125.0
Eclipse Che 7.125.0

3 hours ago

Enhancements

Monitor and expand workspace storage from the Workspace Details page

To avoid workspaces that fail to start with no space left on device, a new Storage tab on the Workspace Details page lets you monitor the workspace persistent volume claim (PVC). You can grow the PVC without leaving the dashboard.

The tab reports the PVC name, its capacity, and live usage measured inside the workspace container. You can add space with a one-click or choose a size in the resize dialog. Because expanding a PVC cannot be undone, the resize dialog requires an explicit confirmation.

Screenshot 2026-11-11 at 16 13 46

Alignment with 1.143.1 version of VS Code

This release updates Visual Studio Code - Open Source ("Code - OSS") to the 1.143.1 upstream version. For more details, see the official release notes.

Increase the default workspace inactivity timeout to one hour

To reduce premature idling of active work, this release increases the default workspace inactivity timeout from 30 minutes to 1 hour for new installations. Explicitly configured timeouts are unaffected. Existing CheCluster resources keep their previously stored value. To adopt the new default on an existing cluster, set spec.devEnvironments.secondsOfInactivityBeforeIdling to 3600.

DevWorkspace Operator 1.1.0

DevWorkspace Operator 1.1.0 is included in this release. For the full list of changes, see the DevWorkspace Operator 1.1.0 changelog.

Control whether the internal OpenVSX registry is enabled on new installations

The default state of the embedded OpenVSX registry is driven by the CHE_DEFAULT_SPEC_COMPONENTS_OPENVSX_REGISTRY_ENABLED operator environment variable instead of a hardcoded custom resource definition (CRD) default. This lets administrators and downstream distributions set the out-of-the-box behavior for new installations. Existing CheCluster resources are unaffected. This is a step toward enabling the internal OpenVSX registry by default. The legacy plugin registry remains available as an opt-in fallback and will be removed in a future release.

Bug Fixes

Fix fetching the self-signed certificate from the Che endpoint

Before this update, the operator could fail to fetch the self-signed certificate from the Che endpoint on some clusters (for example, ROSA), leaving the certificate unavailable to workspaces. With this update, the certificate-fetching logic reliably retrieves the certificate from the endpoint. As a result, the self-signed certificate is resolved correctly across these cluster types.

Fixes #24010.

Devfiles in repositories hosted on private Git servers are honored again

A destination check introduced in Che 7.123 rejected Git hosts that are not publicly routable before devfile discovery ran. As a result, creating a workspace from an internal GitHub Enterprise, GitLab Server, or Bitbucket Server instance silently ignored the repository's devfile and fell back to a default workspace. With this update, repositories on such servers have their devfiles fetched and applied as before.

Factory URLs that point into a subdirectory respect the devfile's revision

A GitHub tree or blob URL did not say where the branch name ends and a path begins, so the parser treated the whole tail as the branch. A factory URL pointing into a subdirectory produced a branch that does not exist, overriding the devfile's projects[].git.checkoutFrom.revision and leaving the workspace on the default branch. With this update, the parser resolves the ambiguity against the Git API and tracks the subdirectory separately. If the API cannot be reached, the previous behavior is kept.

Publish extensions to OpenVSX from behind a cluster proxy

On clusters configured with a cluster-wide egress proxy, the OpenVSX publisher job did not receive the HTTP_PROXY, HTTPS_PROXY, and NO_PROXY variables. As a result, the publisher ran curl directly and failed with Could not resolve host: open-vsx.org, leaving the job in an Error state and no extensions published. With this update, the publisher job and its pods inherit the cluster proxy configuration.

Git provider access tokens predating the provider-name annotation are found again

Secret lookup read the OAuth provider name only from the che.eclipse.org/scm-provider-name annotation. Secrets created before that annotation existed keep the provider name in che.eclipse.org/scm-personal-access-token-name, so they stopped matching. As a result, the Git Config tab in User Preferences came up empty for personal access tokens added against self-hosted providers. With this update, the lookup falls back to the token name when the provider-name annotation is missing or empty.

Don't miss a new che release

NewReleases is sending notifications on new releases.