Cleanup/remove editors and tools build - #2114
Conversation
…hing The plugin registry now serves only OpenVSX extensions. Editor definitions (che-editors.yaml) were the only consumer of the tools/build npm package and the content publishing infrastructure (surge, gh-pages). Removed: - che-editors.yaml and v3/ directory (editor definitions and icons) - tools/build/ npm package and all root yarn/npm files - Workflows: typescript-pr-check, regen-yarn-lock-and-copy, publish-pr-check-content, publish-content-push-main - build/dev/publish-plugin-registry-to-gh-pages.sh - Editor content extraction from image-build-pr-check and release workflows - Python/yq setup from release workflow (only needed for che-editors.yaml) - .vscode/ settings (referenced .yarn SDKs) Updated: - build.sh: removed yarn/tools steps and --offline/--skip-digest-generation flags - Dockerfile: removed COPY of output/v3, v3/plugins, v3/images - Deploy manifests: health check path changed from /v3/plugins/ to / - make-release.sh: replaced updateEditors with simple VERSION bump - README.md, CONTRIBUTE.md, .htaccess, dependabot.yml, .linelint.yml Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Signed-off-by: Valerii Svydenko <vsvydenk@redhat.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Signed-off-by: Valerii Svydenko <vsvydenk@redhat.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: svor The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Signed-off-by: Valerii Svydenko <vsvydenk@redhat.com>
|
This PR contains changes to files in directories that are typically not intended to be committed:
Please verify these changes are intentional. |
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Signed-off-by: Valerii Svydenko <vsvydenk@redhat.com>
|
@svor: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Summary
The plugin registry's sole purpose is now serving OpenVSX extensions for air-gapped/offline environments. This PR removes all editor definition infrastructure and Node.js build tooling that are no longer needed.
What's removed
Editor definitions: che-editors.yaml and v3/ directory (editor icons, plugins .htaccess)
Node.js tooling: tools/build/ npm package, root package.json, yarn.lock, .yarnrc.yml, .yarn/, .vscode/
Content publishing infrastructure: publish-pr-check-content, publish-content-push-main workflows, build/dev/publish-plugin-registry-to-gh-pages.sh, surge.sh deployment
Supporting workflows: typescript-pr-check, regen-yarn-lock-and-copy
Internal Red Hat downstream build references from README
release.yml: removed Python/yq setup, gh-pages publishing, publishToGhPages input
image-build-pr-check.yml: removed node/yarn setup, content artifact extraction, pull-request-info job
next-build.yml: removed node/yarn setup
README.md, CONTRIBUTE.md, .htaccess, dependabot.yml, .linelint.yml: cleaned up stale references
What's kept
registry
rework)