Major Enhancements
Support for JetBrains Gateway 2025
With this release, JetBrains Gateway 2025 is supported by the dedicated plugin, which is compatible with Eclipse Che.
Allow filtering samples by tags and languages on the User Dashboard
With this release, you can filter samples on the User Dashboard by both tags and languages.
Use UDI 9 as the default development image
With this release, quay.io/devfile/universal-developer-image:ubi9-latest is used as the default development image. To override it, use the spec.devEnvironments.defaultComponents Custom Resource property:
spec:
devEnvironments:
defaultComponents:
- name: universal-developer-image
container:
image: <>
Add NodeJS MongoDB sample in Eclipse Che website
A new Node.js MongoDB sample that has been contributed to devfile.io is available on the Eclipse Che official website with this release.
Resource requirements for running a CDE with a JetBrains IDE
Information about additional memory and CPU requirements for a JetBrains IDE (e.g. IntelliJ IDEA Ultimate) is available in the official documentation.
Bug Fixes
Workspaces which used ubi9-based samples as tool containers failed to start with JetBrains IntelliJ IDEA (desktop)
Before this release, there was a known issue with starting Cloud Development Environments (CDEs) created with ubi9-based images (ubi9-minimal, ubi-init, and ubi9) in the desktop version of JetBrains IntelliJ IDEA. The IDE did not load, causing the start of the workspace to fail after some time. The defect has been fixed in this release.
Git history wiped out after workspace pod crash
Previously, there was a defect related to the loss of all Git history if a workspace pod was restarted with a default devfile when the persistent storage strategy specified in the CheCluster was per-workspace. The defect has been fixed in this release.
Setting controller.devfile.io/storage-type attribute to ephemeral in devfile doesn't use ephemeral storage
The regression related to the controller.devfile.io/storage-type: ephemeral attribute has been fixed in this release, and Cloud Development Environments (CDEs) created from devfiles with this attribute now correctly use the emptyDir volumes.
Error redirect page when accepting OAuth2 factory on Bitbucket server
Previously, when accepting Bitbucket server's OAuth2 prompt, there was an unexpected error redirect page with the error stack trace: {"message":"Cannot invoke \"String.length()\" because \"this.input\" is null","trace"}. The defect has been fixed in this release.
Gitlab raw devfile url is not recognized
Previously, Gitlab raw devfile URLs were not correctly processed, resulting in the default devfile being used for Cloud Development Environment (CDE) startup. The defect has been fixed in this release.
Gitlab repository URL with multiple groups and subgroups is corrupted
Previously, when you launched a workspace from the Dashboard using a Gitlab repository URL with multiple groups and subgroups, it failed when a branch from the Git Repo Options was also provided from the Dashboard. The defect has been fixed in this release.
Bitbucket SSH URL to create workspace not working
Before this release, you could not create a Cloud Development Dnvironment (CDE) based on Bitbucket SSH URLs because the startup was interrupted by the Warning alert:Failed to create the workspace error. The defect has been fixed in this release.
Post start events execute in alphabetic order rather than listed sequence, leading to potential confusion
Previously, postStart commands were executed based on alphabetical order rather than the sequence in which they were listed in the devfile, leading to potential confusion, especially when a specific execution order is expected based on the listed sequence. Starting from this release, the execution happens in sequential order in the way the commands are listed in the postStart section of a devfile:
postStart:
- command-one
- command-two
- command-three
Pre-release versions of the extensions are installed by default from https://open-vsx.org
Previously, the pre-release versions of the extensions were installed by default from https://open-vsx.org. The defect has been fixed in this release, and now the stable versions of the extensions are installed by default.