Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
36724
ab315327 cleanup(devkit): use readJson to read the installed package version from the tree [Self-Healing CI Rerun]
by nx-cloud[bot]
Failed
36724
Flaky task→
eec419fa cleanup(devkit): use readJson to read the installed package version from the tree [Self-Healing CI Rerun]
by nx-cloud[bot]
Failed
36724
Flaky task→
4d341573 cleanup(devkit): use readJson to read the installed package version from the tree
by Leosvel Pé...
Failed
36724
Flaky task→
4d341573 cleanup(devkit): use readJson to read the installed package version from the tree
by Leosvel Pé...
Succeeded
36724
b431a3fc cleanup(devkit): correct getInstalledPackageVersion JSDoc for generator-time fallback
by Leosvel Pé...
Failed
36724
Flaky task→
b431a3fc cleanup(devkit): correct getInstalledPackageVersion JSDoc for generator-time fallback
by Leosvel Pé...
Succeeded
36724
dc4f8f31 fix(devkit): correct version floor validation for ranges and prereleases Generators calling assertSupportedPackageVersion rejected workspaces declaring a version range that a supported installed version satisfies. `@nx/js:typescript-sync` reported an unsupported typescript version for a declared range of ">=4.8.4 <6.1.0" with TypeScript 6.0.2 installed, because the declared range was coerced to its first version token (4.8.4) and compared to the 5.8.0 floor. The assertion now resolves the installed version first and lets it decide when it satisfies the declared range. It reads the tree's node_modules and falls back to workspace-root module resolution for installs without a node_modules layout, e.g. Yarn PnP. Prereleases count as their release version throughout. A declared range that cannot reach the floor still fails as unsupported. A range that straddles the floor without a resolvable install fails asking to install dependencies first, since the lockfile may pin either side; this is reachable with .nx/installation setups where plugins run before workspace packages are installed.
by Leosvel Pé...