Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
35631
7245558d fix(core): handle local plugin subpath dist fallback
by Leosvel Pé...
Failed
35631
Fix applied→
7245558d fix(core): handle local plugin subpath dist fallback
by Leosvel Pé...
Failed
35631
94e18fdd fix(core): handle local plugin subpath dist fallback
by Leosvel Pé...
Failed
35631
53b94d79 fix(core): handle local plugin subpath dist fallback
by Leosvel Pé...
Succeeded
35631
53b94d79 fix(core): handle local plugin subpath dist fallback
by Leosvel Pé...
Failed
35631
53b94d79 fix(core): handle local plugin subpath dist fallback
by Leosvel Pé...
Succeeded
35631
42b1c5e3 fix(core): resolve local plugin subpath imports from source Local plugins imported via subpath exports (e.g. `@scope/pkg/cypress`) collapsed onto the project's build-target `main`, ignoring the requested subpath and silently loading the wrong source file. Resolve subpath imports against the project's `package.json` `exports` using the workspace's `customConditions` (plus `development` as backward-compat for pre-21.5 setups). Hard-fail with guidance when no source-pointing condition is declared instead of falling through to a mismatched fallback. Hoist local-source resolution ahead of `require.resolve` so workspace plugins prefer the source-pointing condition over the symlinked `dist` that Node's resolver would otherwise pick up via `default` (Node ignores TypeScript custom conditions). Default plugins (absolute paths) and external installed packages skip this branch to avoid recursing through project loading. Update `schema-utils` to also honor the workspace's `customConditions` when resolving executor/generator implementations from source.
by Leosvel Pé...
Failed
35631
Flaky task→
42b1c5e3 fix(core): resolve local plugin subpath imports from source Local plugins imported via subpath exports (e.g. `@scope/pkg/cypress`) collapsed onto the project's build-target `main`, ignoring the requested subpath and silently loading the wrong source file. Resolve subpath imports against the project's `package.json` `exports` using the workspace's `customConditions` (plus `development` as backward-compat for pre-21.5 setups). Hard-fail with guidance when no source-pointing condition is declared instead of falling through to a mismatched fallback. Hoist local-source resolution ahead of `require.resolve` so workspace plugins prefer the source-pointing condition over the symlinked `dist` that Node's resolver would otherwise pick up via `default` (Node ignores TypeScript custom conditions). Default plugins (absolute paths) and external installed packages skip this branch to avoid recursing through project loading. Update `schema-utils` to also honor the workspace's `customConditions` when resolving executor/generator implementations from source.
by Leosvel Pé...