-
Task
-
Resolution: Done
-
Major
-
3.6.0.GA
-
productization: build & internals, Team A: Dashboard, devfile and plugin registries, open-vsx, operator + chectl/dsc, devfile-converter, configbump + traefik, image-puller, server, gateway, authentication, try-in-web-ide action, telemetry, Team B: DevWorkspace + Operator, Web Terminal + Operator, editors/IDEs + built-in vscode extensions, Universal Developer Image, machine-exec, dev environment config
-
None
-
False
-
None
-
False
-
-
1. Need to have a source of truth for the current version of vscode being built into che-code / devspaces-code image
2. when building the plugin registry, need to check that the vsix files contain compatible metadata stating that these extensions can run on vscode version ____ or greater
- Check package.json ==> .engines.vscode ==> https://github.com/redhat-developer/vscode-java/pull/2951/files
3. if an incompatibility is found, fail the build immediately
Could also consider implementing this as a PR check upstream, assuming we plan to switch to "embedded registry" as the default in CheCluster as of 7.64.
- is related to
-
CRW-4111 Installation of Python and Jupyter extensions fail in DS 3.5.0 on airgap cluster
- Closed
-
CRW-4115 Unit / Integration test for plugin registry: can all the included plugins be installed
- Closed
- relates to
-
CRW-4049 Create jenkins build for vsix plugins, publishing to download.devel
- Resolved
- links to