Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
36686
d1f8236f fix(release): deduplicate devkit imports [Self-Healing CI Rerun]
by nx-cloud[bot]
Failed
36686
Flaky task→
18d462dc fix(release): deduplicate devkit imports [Self-Healing CI Rerun]
by nx-cloud[bot]
Failed
36686
Flaky task→
18d462dc fix(release): deduplicate devkit imports [Self-Healing CI Rerun]
by nx-cloud[bot]
Succeeded
36686
2c7ed812 fix(release): deduplicate devkit imports [Self-Healing CI Rerun]
by nx-cloud[bot]
Failed
36686
68c85512 fix(release): deduplicate devkit imports Co-authored-by: leosvelperez <leosvelperez@users.noreply.github.com>
by nx-cloud[bot]
Failed
36686
Flaky task→
68c85512 fix(release): deduplicate devkit imports Co-authored-by: leosvelperez <leosvelperez@users.noreply.github.com>
by nx-cloud[bot]
Canceled
36686
ad1151fd fix(js): handle workspace package aliases in deploy executors The prune-lockfile executor rewrote aliased workspace dependencies to file:./workspace_modules/<alias-key>, a directory that never exists (modules are copied under their package names), and left npm: aliases pointing at the registry. The copy-workspace-modules executor matched workspace packages by the raw manifest key, so aliased dependencies were never copied and nested aliased entries kept their workspace: specifiers in the copied manifests. Both executors now resolve entries through resolveWorkspaceDependencyTarget: alias keys are kept and pointed at the target package's module dir, and the target modules are copied.
by Leosvel Pé...
Failed
36686
Fix applied→
ad1151fd fix(js): handle workspace package aliases in deploy executors The prune-lockfile executor rewrote aliased workspace dependencies to file:./workspace_modules/<alias-key>, a directory that never exists (modules are copied under their package names), and left npm: aliases pointing at the registry. The copy-workspace-modules executor matched workspace packages by the raw manifest key, so aliased dependencies were never copied and nested aliased entries kept their workspace: specifiers in the copied manifests. Both executors now resolve entries through resolveWorkspaceDependencyTarget: alias keys are kept and pointed at the target package's module dir, and the target modules are copied.
by Leosvel Pé...
Failed
36686
Generating fix→
ad1151fd fix(js): handle workspace package aliases in deploy executors The prune-lockfile executor rewrote aliased workspace dependencies to file:./workspace_modules/<alias-key>, a directory that never exists (modules are copied under their package names), and left npm: aliases pointing at the registry. The copy-workspace-modules executor matched workspace packages by the raw manifest key, so aliased dependencies were never copied and nested aliased entries kept their workspace: specifiers in the copied manifests. Both executors now resolve entries through resolveWorkspaceDependencyTarget: alias keys are kept and pointed at the target package's module dir, and the target modules are copied.
by Leosvel Pé...