Chapter 3. Bug fixes 3.1. Allowlist Kubernetes service in 'no_proxy' environment variable Starting from this release, there is a dedicated warning message for clusters that are behind a proxy, if you did not add the KUBERNETES_SERVICE_HOST environment variable to the no_proxylist environment variable. Additional resources CRW-7514 3.2. Unexpected warning message while try to start a workspace from a raw devfile Previously, a sporadic warning message could show up while Cloud Development Environment (CDE) was starting from a raw devfile. The defect has been fixed in this release. Additional resources CRW-7848 3.3. DevWorkspace 'storage-type' attribute temporarily removed when restarting from local devfile Previously, the DevWorkspace 'storage-type' attribute was temporarily removed when restarting the Cloud Development Environment (CDE) from the local devfile. The defect has been fixed in this release. Additional resources CRW-8216 3.4. GitHub authorization does not work properly Previously, revoking the GitHub token from the dashboard could fail with an "OAuth token for provider GitHub was not found" error message under certain conditions. The defect has been fixed in this release. Additional resources CRW-8218 3.5. An error appears when accessing the User Preferences Git Services tab Previously, under certain conditions, a "TypeError: Cannot assign to read only property 0 of object `[objectArray]`" error message would appear when navigating to the User Preferences Git Services tab. The defect has been fixed in this release. Additional resources CRW-8219 3.6. Factory from Bitbucket server private repository based on SSH URL has an unexpected warning Before this release, when you started a Cloud Development Environment (CDE) for a Bitbucket server private repository based on an SSH URL, the start was interrupted with an unexpected warning. The defect has been fixed in this release. Additional resources CRW-8220 3.7. Automatically restart from local devfile when devfile failed to be resolved at startup for SSH URLs Regression related to the automatic restart from the local devfile for SSH URLs has been fixed in this release. Additional resources CRW-8224 3.8. Kubeconfig format corruption after switching clusters and restarting workspace Kubeconfig format corruption after switching clusters and restarting the Cloud Development Environment (CDE) has been fixed in this release. Additional resources CRW-8225 3.9. Can not create a workspace using SSH Previously, there was a "Cannot add property controller.devfile.io/bootstrap-devworkspace, object is not extensible" error when you tried to create a workspace with an SSH URL from the Dev Spaces dashboard. This defect has been fixed in this release. Additional resources CRW-8227 3.10. Current stow implementation in udi8/9 will break under certain conditions Previously if devEnvironments.persistUserHome.enabled and devEnvironments.persistUserHome.disableInitContainer were both true , and if there was a file in the /home/user directory that would cause a stow conflict, the stow command would still run and fail due to the conflict. With this release, UBI and UDI entrypoint automatically add conflicting files into the /home/tooling/.stow-local-ignore to prevent the stow failure. Additional resources CRW-8228 3.11. Use current project directory at terminal creation When creating new terminals in the Visual Studio Code - Open Source ("Code - OSS") editor with the New Terminal (Select a Container) option, the initial directory was not the current project directory (ex. /projects/<project-name> ). This defect has been fixed in this release. Additional resources CRW-8229 3.12. Outdated Visual Studio Code - Open Source ("CODE - OSS") appears in workspaces created in Dev Spaces version Before this release, there was an issue affecting Visual Studio Code - Open Source ("CODE - OSS") after you upgraded Dev Spaces from version 3.17.0 to 3.18.0. An outdated version of the IDE appeared when you opened a workspace previously created from a sample in Dev Spaces 3.17.0. This issue has been fixed in this release. Additional resources CRW-8309 3.13. Git user.name and user.email not set up automatically Before this release, there was an issue affecting the automatic setup of Git user.name and user.email in the `gitconfig file after you configured your access token (PAT) or OAuth. If you opened User Dashboard > Gitconfig page after PAT or OAuth configuration, you received the following error message: "Author identity unknown." The issue has been solved in this release. Additional resources CRW-8310

Commands: