Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
36654
601de4a5 cleanup(linter): remove a duplicated lint-utils test and clarify docs [Self-Healing CI Rerun]
by nx-cloud[bot]
Failed
36654
Flaky task→
fb6c9d97 cleanup(linter): remove a duplicated lint-utils test and clarify docs Dropping the imp parameter from hasBannedDependencies left two tests with identical inputs and expectations, so one is removed. The isConstraintBanningProject parameter is renamed to importSpecifier since it receives the bare package name on the nested path. The checkNestedExternalImports docs now state that nested matching is package-granular.
by Leosvel Pé...
Failed
36654
Flaky task→
fb6c9d97 cleanup(linter): remove a duplicated lint-utils test and clarify docs Dropping the imp parameter from hasBannedDependencies left two tests with identical inputs and expectations, so one is removed. The isConstraintBanningProject parameter is renamed to importSpecifier since it receives the bare package name on the nested path. The checkNestedExternalImports docs now state that nested matching is package-granular.
by Leosvel Pé...
Canceled
36654
952e72b1 cleanup(linter): remove a duplicated lint-utils test and clarify docs Dropping the imp parameter from hasBannedDependencies left two tests with identical inputs and expectations, so one is removed. The isConstraintBanningProject parameter is renamed to importSpecifier since it receives the bare package name on the nested path. The checkNestedExternalImports docs now state that nested matching is package-granular.
by Leosvel Pé...
Succeeded
36654
636cacc7 fix(linter): apply allowed external imports to nested dependencies The nested external-import check only ran for constraints with a bannedExternalImports list. That gate predates allowedExternalImports, so an allowed-only constraint never checked the transitive external dependencies of imported projects, while a direct import of a package outside the list was reported. The gate now accepts an allowed list too, including an empty one, which bans every external package.
by Leosvel Pé...
Failed
36654
Flaky task→
636cacc7 fix(linter): apply allowed external imports to nested dependencies The nested external-import check only ran for constraints with a bannedExternalImports list. That gate predates allowedExternalImports, so an allowed-only constraint never checked the transitive external dependencies of imported projects, while a direct import of a package outside the list was reported. The gate now accepts an allowed list too, including an empty one, which bans every external package.
by Leosvel Pé...
Succeeded
36654
fe674c7e fix(linter): apply allowed external imports to nested dependencies The nested external-import check only ran for constraints with a bannedExternalImports list. That gate predates allowedExternalImports, so an allowed-only constraint never checked the transitive external dependencies of imported projects, while a direct import of a package outside the list was reported. The gate now accepts an allowed list too, including an empty one, which bans every external package.
by Leosvel Pé...
Failed
36654
Flaky task→
fe674c7e fix(linter): apply allowed external imports to nested dependencies The nested external-import check only ran for constraints with a bannedExternalImports list. That gate predates allowedExternalImports, so an allowed-only constraint never checked the transitive external dependencies of imported projects, while a direct import of a package outside the list was reported. The gate now accepts an allowed list too, including an empty one, which bans every external package.
by Leosvel Pé...
Succeeded
36654
c46db6be fix(linter): flag banned external imports reached through internal projects With checkNestedExternalImports enabled, importing an internal project whose transitive dependencies include a package listed in bannedExternalImports never produced a violation. The subpath-matching guard added to isConstraintBanningProject for deep import bans compares the original import specifier against the external package name, and on the nested path that specifier names the imported internal project, so the guard never matched and the nested check was dead. Match transitive external dependencies against the external package's own name instead of the original import specifier, restoring the behavior the nested check had before the guard was introduced. The direct import path keeps the specifier-based subpath matching.
by Leosvel Pé...
Succeeded
36654
01d685d1 fix(linter): flag banned external imports reached through internal projects With checkNestedExternalImports enabled, importing an internal project whose transitive dependencies include a package listed in bannedExternalImports never produced a violation. The subpath-matching guard added to isConstraintBanningProject for deep import bans compares the original import specifier against the external package name, and on the nested path that specifier names the imported internal project, so the guard never matched and the nested check was dead. Match transitive external dependencies against the external package's own name instead of the original import specifier, restoring the behavior the nested check had before the guard was introduced. The direct import path keeps the specifier-based subpath matching.
by Leosvel Pé...
Succeeded
36654
47a65a03 fix(linter): flag banned external imports reached through internal projects With checkNestedExternalImports enabled, importing an internal project whose transitive dependencies include a package listed in bannedExternalImports never produced a violation. The subpath-matching guard added to isConstraintBanningProject for deep import bans compares the original import specifier against the external package name, and on the nested path that specifier names the imported internal project, so the guard never matched and the nested check was dead. Match transitive external dependencies against the external package's own name instead of the original import specifier, restoring the behavior the nested check had before the guard was introduced. The direct import path keeps the specifier-based subpath matching.
by Leosvel Pé...