You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
refactor(e2e): single populate script, @cluster-free tag scoping, review fixes
Apply the code-review findings on the cluster-free harness:
- Extract the dynamic-plugins-root populate step into
e2e-tests/local-harness/populate.sh — the single source of truth used by
CI, the docs, and the global-setup error message (they had already
diverged: CI installed the harness OCI set pinned to CLI 0.2.0 while the
docs/error message pointed at the catalog index, unversioned).
- Drop the unused CATALOG_INDEX_IMAGE env from the workflow: with the
harness dynamic-plugins.yaml (no includes), the CLI only used it to
extract a catalog index that nothing consumed — a wasted :latest quay
pull on every run. Fix the workflow header comment accordingly (plugins
come from ghcr OCI, not the catalog index).
- Scope the harness run by a @cluster-free test tag instead of a title
regex; widening coverage is now tagging the validated test and
allowlisting its spec file in testMatch.
- Count only directories in the global-setup guard: the installer writes
its generated global-config file into dynamic-plugins-root even when
zero plugins install, which previously satisfied the guard and produced
the confusing locator timeout it exists to prevent.
- Rewrite the docs populate section: the OCI/populate.sh path (what CI
uses, works from a fresh clone) is primary; the catalog-index path is
demoted to after-source-build use since its default.yaml references
./dynamic-plugins/dist paths that don't exist otherwise.
- Gitignore the root dynamic-plugins.yaml copy the populate script leaves
behind (the CLI hardcodes that path).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
0 commit comments