Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
36316
802a5693 cleanup(vitest): clarify root config classification and tighten its tests Name the root-config classifier's return as a `'declares' | 'missing' | 'unknown'` union so the three cases read explicitly at the call sites and a later truthiness check can't fold `'unknown'` in with the aggregating case. Correct the aggregator comment to note its projects glob matches the generated `vitest.config.ts` itself (excluded now), not only a root `vite.config` added later. Add a test for a root `vitest.config.ts` that already declares `test.projects` (left untouched, no warning), and drop an unreachable `?? {}` fallback in the plugin's no-node assertions.
by Leosvel Pé...
Succeeded
36316
528f2a92 cleanup(vitest): cover root config selection edge cases The configuration generator picks between a v4 root vitest.config.ts, a v3 vitest.workspace.ts, and skipping when a root config already exists, but two branches of that selection had no direct coverage. Add tests that the generator skips writing vitest.config.ts when a root vite.config.ts is already present, and that it defaults to the v4 root-config shape when the installed vitest version cannot be detected.
by Leosvel Pé...
Failed
36316
Environment issue→
b69b03e0 cleanup(vitest): cover root config selection edge cases The configuration generator picks between a v4 root vitest.config.ts, a v3 vitest.workspace.ts, and skipping when a root config already exists, but two branches of that selection had no direct coverage. Add tests that the generator skips writing vitest.config.ts when a root vite.config.ts is already present, and that it defaults to the v4 root-config shape when the installed vitest version cannot be detected.
by Leosvel Pé...
Failed
36316
a86ffff1 fix(vite): exclude the migrated root vitest config from its own glob The vitest 4 migration inlines a static vitest.workspace file into a root vitest.config under test.projects. The inlined `**/vitest.config.*` glob matched the new config itself, so vitest resolved the root config as an extra project. With no include of its own, that project re-ran every test through the default glob without each project's environment and setupFiles, duplicating runs and failing tests that depend on their own config. Both write paths now append a root-anchored negative glob excluding the root config file (`!vitest.config.<ext>`). The create path applies it unconditionally; the merge path (editing a pre-existing config) applies it only when the target has no own `test.include`, since a config that runs its own tests must stay in the project set. The negation only ever drops the root file and is inert when the globs don't match it. The AI migration instructions gain the same self-match check next to the existing duplicate-name one.
by Leosvel Pé...
Failed
36316
c2989945 fix(vite): exclude the migrated root vitest config from its own glob The vitest 4 migration inlines a static vitest.workspace file into a root vitest.config under test.projects. The inlined `**/vitest.config.*` glob matched the new config itself, so vitest resolved the root config as an extra project. With no include of its own, that project re-ran every test through the default glob without each project's environment and setupFiles, duplicating runs and failing tests that depend on their own config. Both write paths now append a root-anchored negative glob excluding the root config file (`!vitest.config.<ext>`). The create path applies it unconditionally; the merge path (editing a pre-existing config) applies it only when the target has no own `test.include`, since a config that runs its own tests must stay in the project set. The negation only ever drops the root file and is inert when the globs don't match it. The AI migration instructions gain the same self-match check next to the existing duplicate-name one.
by Leosvel Pé...