Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Failed
35671
Fix available→
398101e0 chore(testing): refine vitest 3/4 AI migration prompts for accuracy and steering - correct vitest 4 browser provider example (function from per-provider package) - fix pool options example: singleFork:true -> maxWorkers:1, isolate:false - add vitest 4 prerequisites (Vite >=6, Node >=20) and exclude-defaults narrowing - add Nx-specific notes (inferred plugin targets, shared base config, Analog) - cover transformMode -> viteEnvironment, deps.optimizer.web -> .client - snapshot section: correct printShadowRoot placement, add Snapshots import, vi.fn string change - reporter API: include all five removed callbacks with concrete replacements - vitest 3: clarify v3.2 workspace option rename vs v4 file removal - vitest 3: clarify browser.name/providerOptions deprecation vs removal - correct mockRestore wording (single-spy mockRestore still works in v4)
by Leosvel Pé...
Failed
35671
402dd1bb feat(testing): add Vitest 1.x/2.x -> v3 floor and v3 -> v4 migrations - packageJsonUpdates force v1/v2 -> v3, then v3 -> v4 cascade for Nx 23.x - AI-instructions prompts for vitest 3 (new) and vitest 4 (duplicated from @nx/vitest) - lives in @nx/vite so pre-22.2.0 users (no @nx/vitest installed yet) are reached
by Leosvel Pé...
Succeeded
35671
93e301c4 chore(testing): adopt cypress version-resolution pattern in @nx/vitest - versions(tree) returns a 3-key bundle of vitest deps that vary per major (vitestVersion, vitestCoverageV8Version, vitestCoverageIstanbulVersion); stable deps stay as top-level exports. - Drop isVitestV3, getVitestDependenciesVersionsToInstall, and the per-major aliases (vitestV3Version, vitestV4Version, vitestV{3,4}CoverageV8Version, vitestV{3,4}CoverageIstanbulVersion). No external consumers in the repo. - Tree-less getInstalledVitestVersion(tree?) routes through getInstalledPackageVersion from @nx/devkit/internal. - Move version-utils.ts's vitest helpers into versions.ts; only the vite-domain helpers (getInstalledViteVersion, getInstalledViteMajorVersion) remain there.
by Leosvel Pé...
Failed
35671
Flaky task→
93e301c4 chore(testing): adopt cypress version-resolution pattern in @nx/vitest - versions(tree) returns a 3-key bundle of vitest deps that vary per major (vitestVersion, vitestCoverageV8Version, vitestCoverageIstanbulVersion); stable deps stay as top-level exports. - Drop isVitestV3, getVitestDependenciesVersionsToInstall, and the per-major aliases (vitestV3Version, vitestV4Version, vitestV{3,4}CoverageV8Version, vitestV{3,4}CoverageIstanbulVersion). No external consumers in the repo. - Tree-less getInstalledVitestVersion(tree?) routes through getInstalledPackageVersion from @nx/devkit/internal. - Move version-utils.ts's vitest helpers into versions.ts; only the vite-domain helpers (getInstalledViteVersion, getInstalledViteMajorVersion) remain there.
by Leosvel Pé...
Succeeded
35671
f978e205 fix(testing): multi-version support compliance for @nx/vitest Adds floor-enforcement asserts (>= 2.0.0) to all generators via a new `assertSupportedVitestVersion` wrapper backed by the shared devkit helper, and a parameterized floor spec. Preserves user pins in init (`keepExistingVersions` default flipped to `true`). Drops `^1.0.0` from the `vitest` peer range. The plugin has no v1 install lane (no `isVitestV1` branch, no v1 install constants), so v1 workspaces were silently falling through to v4 install constants. Aligning peer with the implemented lanes (v2/v3/v4) makes the supported range honest. Tightens migration `requires` gates to follow the precise applicability pattern used elsewhere (e.g. @nx/angular): the Vitest 4 AI-instructions migrations gate on `vitest: ">=4.0.0"`. The reportsDirectory and gitignore migrations are version-agnostic transformations and need no `requires`.
by Leosvel Pé...
Failed
35671
Flaky task→
f978e205 fix(testing): multi-version support compliance for @nx/vitest Adds floor-enforcement asserts (>= 2.0.0) to all generators via a new `assertSupportedVitestVersion` wrapper backed by the shared devkit helper, and a parameterized floor spec. Preserves user pins in init (`keepExistingVersions` default flipped to `true`). Drops `^1.0.0` from the `vitest` peer range. The plugin has no v1 install lane (no `isVitestV1` branch, no v1 install constants), so v1 workspaces were silently falling through to v4 install constants. Aligning peer with the implemented lanes (v2/v3/v4) makes the supported range honest. Tightens migration `requires` gates to follow the precise applicability pattern used elsewhere (e.g. @nx/angular): the Vitest 4 AI-instructions migrations gate on `vitest: ">=4.0.0"`. The reportsDirectory and gitignore migrations are version-agnostic transformations and need no `requires`.
by Leosvel Pé...