Overview - Nx

Nx

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Failed
33562
Fix ready→
96e77789 fix(core): revise to match
12 hours ago by comp615
Succeeded
master
d5bd57e6 fix(core): include PNPM patches in externalDependencies hash computations (#33551) ## Current Behavior If a workspace uses pnpm and adds a local patch to a dependency (e.g. `vitest`), this patch is not taken into account when computing that dependency's hash for purposes of determining cache changes. In practice, you could patch vitest locally, and tests would pull from the cache. ## Expected Behavior Patches can alter behavior in the same way that updating the version could, it's just that the version is not created and the patch is applied locally. This updates the pnpm lockfile parsing functionality to read the patches field into a map and then combine the patch hash with the integrity hash. The integrity hash ONLY represents the remote / tarball intergrity, so these have to be combined in order to create a proper key. ## Related Issue(s) (Could not find any, but saw this in my work today) --------- Co-authored-by: Leosvel Pérez Espinosa <leosvel.perez.espinosa@gmail.com>
14 hours ago by comp615
Failed
33562
b584d735 fix(core): revise to match
17 hours ago by comp615
Failed
33562
b584d735 fix(core): revise to match
19 hours ago by comp615
Succeeded
master
d5bd57e6 fix(core): include PNPM patches in externalDependencies hash computations (#33551) ## Current Behavior If a workspace uses pnpm and adds a local patch to a dependency (e.g. `vitest`), this patch is not taken into account when computing that dependency's hash for purposes of determining cache changes. In practice, you could patch vitest locally, and tests would pull from the cache. ## Expected Behavior Patches can alter behavior in the same way that updating the version could, it's just that the version is not created and the patch is applied locally. This updates the pnpm lockfile parsing functionality to read the patches field into a map and then combine the patch hash with the integrity hash. The integrity hash ONLY represents the remote / tarball intergrity, so these have to be combined in order to create a proper key. ## Related Issue(s) (Could not find any, but saw this in my work today) --------- Co-authored-by: Leosvel Pérez Espinosa <leosvel.perez.espinosa@gmail.com>
1 day ago by comp615
Failed
33572
0a1400b9 fix(core): run post-task lifecycle for run-command parallel exections
2 days ago by comp615
Canceled
master
d5bd57e6 fix(core): include PNPM patches in externalDependencies hash computations (#33551) ## Current Behavior If a workspace uses pnpm and adds a local patch to a dependency (e.g. `vitest`), this patch is not taken into account when computing that dependency's hash for purposes of determining cache changes. In practice, you could patch vitest locally, and tests would pull from the cache. ## Expected Behavior Patches can alter behavior in the same way that updating the version could, it's just that the version is not created and the patch is applied locally. This updates the pnpm lockfile parsing functionality to read the patches field into a map and then combine the patch hash with the integrity hash. The integrity hash ONLY represents the remote / tarball intergrity, so these have to be combined in order to create a proper key. ## Related Issue(s) (Could not find any, but saw this in my work today) --------- Co-authored-by: Leosvel Pérez Espinosa <leosvel.perez.espinosa@gmail.com>
2 days ago by comp615
Failed
33562
59d6c3fc fix(core): include continuous tasks in taskResults
2 days ago by comp615
Failed
33572
0a1400b9 fix(core): run post-task lifecycle for run-command parallel exections
2 days ago by comp615
Succeeded
33551
3f7fcc23 fix(core): handle pnpm patch specifiers
5 days ago by comp615
Failed
33551
c24c7a67 fix(core): include PNPM patches in externalDependncy hash computations
8 days ago by comp615