Overview - Nx

Nx

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
431
67f53a93 fix(schematics) fix ngrx schematics with dash
1 day ago by FrozenPandaz
Succeeded
430
2ab89f14 fix(schematics) use property name in ngrx reducer spec
2 days ago by FrozenPandaz
Succeeded
master
d64e41dd fix(repo): revert sudo for global npm install in publish workflow (#34451) ## Current Behavior The publish workflow uses `sudo npm install -g npm@11.5.2` which was added in #34409. This causes issues with OIDC token permissions in the release pipeline since `sudo` runs as a different user context. ## Expected Behavior The publish workflow should use `npm install -g npm@11.5.2` without `sudo`, matching the standard approach used elsewhere and avoiding permission context issues during release. ## Related Issue(s) Reverts #34409
2 days ago by FrozenPandaz
Succeeded
master
d64e41dd fix(repo): revert sudo for global npm install in publish workflow (#34451) ## Current Behavior The publish workflow uses `sudo npm install -g npm@11.5.2` which was added in #34409. This causes issues with OIDC token permissions in the release pipeline since `sudo` runs as a different user context. ## Expected Behavior The publish workflow should use `npm install -g npm@11.5.2` without `sudo`, matching the standard approach used elsewhere and avoiding permission context issues during release. ## Related Issue(s) Reverts #34409
2 days ago by FrozenPandaz
Failed
34455
Fix ready→
130efe43 fix(core): set windowsHide: true on all child process spawns On Windows, child_process.spawn/fork/exec default to windowsHide: false, which creates a visible console window for each subprocess. This causes command prompt windows to flash during project graph creation and task execution. This change sets windowsHide: true across all spawn/fork/exec calls in the codebase and adds a custom ESLint rule (@nx/workspace/require-windows-hide) to enforce this going forward. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2 days ago by FrozenPandaz
Failed
master
d64e41dd fix(repo): revert sudo for global npm install in publish workflow (#34451) ## Current Behavior The publish workflow uses `sudo npm install -g npm@11.5.2` which was added in #34409. This causes issues with OIDC token permissions in the release pipeline since `sudo` runs as a different user context. ## Expected Behavior The publish workflow should use `npm install -g npm@11.5.2` without `sudo`, matching the standard approach used elsewhere and avoiding permission context issues during release. ## Related Issue(s) Reverts #34409
2 days ago by FrozenPandaz
Succeeded
master
c5e1bedc fix(repo): replace addnab/docker-run-action with direct docker run (#34448) ## Current Behavior The publish workflow uses `addnab/docker-run-action@v3` which is based on `docker:20.10` (Docker API 1.41). GitHub's `ubuntu-24.04` runners now ship Docker Engine 28.x which requires minimum API version 1.44, causing all 4 Linux Docker builds to fail: ``` docker: Error response from daemon: client version 1.41 is too old. Minimum supported API version is 1.44, please upgrade your client to a newer version. ``` Failed run: https://github.com/nrwl/nx/actions/runs/21961139962 ## Expected Behavior Linux Docker builds (x86_64-gnu, x86_64-musl, aarch64-gnu, aarch64-musl) complete successfully using the host's modern Docker CLI. https://github.com/nrwl/nx/actions/runs/21996143819 ## Related Issue(s) The `addnab/docker-run-action` repo is abandoned (last release March 2021, last commit May 2021) with open issues about this exact problem.
2 days ago by FrozenPandaz
Succeeded
master
d64e41dd fix(repo): revert sudo for global npm install in publish workflow (#34451) ## Current Behavior The publish workflow uses `sudo npm install -g npm@11.5.2` which was added in #34409. This causes issues with OIDC token permissions in the release pipeline since `sudo` runs as a different user context. ## Expected Behavior The publish workflow should use `npm install -g npm@11.5.2` without `sudo`, matching the standard approach used elsewhere and avoiding permission context issues during release. ## Related Issue(s) Reverts #34409
2 days ago by FrozenPandaz
Succeeded
master
d64e41dd fix(repo): revert sudo for global npm install in publish workflow (#34451) ## Current Behavior The publish workflow uses `sudo npm install -g npm@11.5.2` which was added in #34409. This causes issues with OIDC token permissions in the release pipeline since `sudo` runs as a different user context. ## Expected Behavior The publish workflow should use `npm install -g npm@11.5.2` without `sudo`, matching the standard approach used elsewhere and avoiding permission context issues during release. ## Related Issue(s) Reverts #34409
2 days ago by FrozenPandaz
Succeeded
master
d64e41dd fix(repo): revert sudo for global npm install in publish workflow (#34451) ## Current Behavior The publish workflow uses `sudo npm install -g npm@11.5.2` which was added in #34409. This causes issues with OIDC token permissions in the release pipeline since `sudo` runs as a different user context. ## Expected Behavior The publish workflow should use `npm install -g npm@11.5.2` without `sudo`, matching the standard approach used elsewhere and avoiding permission context issues during release. ## Related Issue(s) Reverts #34409
3 days ago by FrozenPandaz
Failed
master
d64e41dd fix(repo): revert sudo for global npm install in publish workflow (#34451) ## Current Behavior The publish workflow uses `sudo npm install -g npm@11.5.2` which was added in #34409. This causes issues with OIDC token permissions in the release pipeline since `sudo` runs as a different user context. ## Expected Behavior The publish workflow should use `npm install -g npm@11.5.2` without `sudo`, matching the standard approach used elsewhere and avoiding permission context issues during release. ## Related Issue(s) Reverts #34409
3 days ago by FrozenPandaz
Succeeded
779
3e01a4ec fix(schematics): update jest-preset-angular to 6.0.1
3 days ago by FrozenPandaz
Succeeded
master
d64e41dd fix(repo): revert sudo for global npm install in publish workflow (#34451) ## Current Behavior The publish workflow uses `sudo npm install -g npm@11.5.2` which was added in #34409. This causes issues with OIDC token permissions in the release pipeline since `sudo` runs as a different user context. ## Expected Behavior The publish workflow should use `npm install -g npm@11.5.2` without `sudo`, matching the standard approach used elsewhere and avoiding permission context issues during release. ## Related Issue(s) Reverts #34409
3 days ago by FrozenPandaz
Succeeded
22.5.1
24948ec2 fix(repo): revert sudo for global npm install in publish workflow (#34451) ## Current Behavior The publish workflow uses `sudo npm install -g npm@11.5.2` which was added in #34409. This causes issues with OIDC token permissions in the release pipeline since `sudo` runs as a different user context. ## Expected Behavior The publish workflow should use `npm install -g npm@11.5.2` without `sudo`, matching the standard approach used elsewhere and avoiding permission context issues during release. ## Related Issue(s) Reverts #34409
3 days ago by FrozenPandaz
Succeeded
22.5.x
24948ec2 fix(repo): revert sudo for global npm install in publish workflow (#34451) ## Current Behavior The publish workflow uses `sudo npm install -g npm@11.5.2` which was added in #34409. This causes issues with OIDC token permissions in the release pipeline since `sudo` runs as a different user context. ## Expected Behavior The publish workflow should use `npm install -g npm@11.5.2` without `sudo`, matching the standard approach used elsewhere and avoiding permission context issues during release. ## Related Issue(s) Reverts #34409
3 days ago by FrozenPandaz
Succeeded
master
d64e41dd fix(repo): revert sudo for global npm install in publish workflow (#34451) ## Current Behavior The publish workflow uses `sudo npm install -g npm@11.5.2` which was added in #34409. This causes issues with OIDC token permissions in the release pipeline since `sudo` runs as a different user context. ## Expected Behavior The publish workflow should use `npm install -g npm@11.5.2` without `sudo`, matching the standard approach used elsewhere and avoiding permission context issues during release. ## Related Issue(s) Reverts #34409
3 days ago by FrozenPandaz
Succeeded
34451
e8567783 Revert "fix(repo): use sudo for global npm install in publish workflow (#34409)" This reverts commit e48f2f3a8c60a1880133589afd5ae8aa4e5ba617.
3 days ago by FrozenPandaz
Failed
34446
249eb4d1 chore(testing): update cache assertions for output fingerprinting With output fingerprinting, outputs that already match the cache are left in place instead of being re-copied. Update e2e assertions to expect "existing outputs match the cache, left as is" instead of "local cache" when daemon is disabled or outputs are untouched.
3 days ago by FrozenPandaz
Succeeded
22.5.1
699e8d06 fix(repo): replace addnab/docker-run-action with direct docker run (#34448) ## Current Behavior The publish workflow uses `addnab/docker-run-action@v3` which is based on `docker:20.10` (Docker API 1.41). GitHub's `ubuntu-24.04` runners now ship Docker Engine 28.x which requires minimum API version 1.44, causing all 4 Linux Docker builds to fail: ``` docker: Error response from daemon: client version 1.41 is too old. Minimum supported API version is 1.44, please upgrade your client to a newer version. ``` Failed run: https://github.com/nrwl/nx/actions/runs/21961139962 ## Expected Behavior Linux Docker builds (x86_64-gnu, x86_64-musl, aarch64-gnu, aarch64-musl) complete successfully using the host's modern Docker CLI. https://github.com/nrwl/nx/actions/runs/21996143819 ## Related Issue(s) The `addnab/docker-run-action` repo is abandoned (last release March 2021, last commit May 2021) with open issues about this exact problem. (cherry picked from commit c5e1bedca2a081357134b3634f8c60aff98da91b)
3 days ago by FrozenPandaz
Failed
22.5.x
699e8d06 fix(repo): replace addnab/docker-run-action with direct docker run (#34448) ## Current Behavior The publish workflow uses `addnab/docker-run-action@v3` which is based on `docker:20.10` (Docker API 1.41). GitHub's `ubuntu-24.04` runners now ship Docker Engine 28.x which requires minimum API version 1.44, causing all 4 Linux Docker builds to fail: ``` docker: Error response from daemon: client version 1.41 is too old. Minimum supported API version is 1.44, please upgrade your client to a newer version. ``` Failed run: https://github.com/nrwl/nx/actions/runs/21961139962 ## Expected Behavior Linux Docker builds (x86_64-gnu, x86_64-musl, aarch64-gnu, aarch64-musl) complete successfully using the host's modern Docker CLI. https://github.com/nrwl/nx/actions/runs/21996143819 ## Related Issue(s) The `addnab/docker-run-action` repo is abandoned (last release March 2021, last commit May 2021) with open issues about this exact problem. (cherry picked from commit c5e1bedca2a081357134b3634f8c60aff98da91b)
3 days ago by FrozenPandaz