Overview - Nx

Nx

7 days30 days

Latest CI Pipeline Executions

Exact

Succeeded
215
b9d71fe5 fix(schematics): continue traversing within irrelevant PropertyAssignment nodes
14 days ago by JamesHenry
Succeeded
215
b9d71fe5 fix(schematics): continue traversing within irrelevant PropertyAssignment nodes
18 days ago by JamesHenry
Succeeded
32215
4b9e0779 Merge branch 'master' into angular-remove-common-module
2 months ago by JackWBaker
Succeeded
32215
24a42d10 Merge branch 'master' into angular-remove-common-module
2 months ago by JackWBaker
Failed
32215
e730c772 cleanup(angular): remove CommonModule from component generators
2 months ago by JackWBaker
Succeeded
32155
b85d669e docs(nx-cloud): update pricing link in launch templates Co-authored-by: Nicole Oliver <nicole.oliver.42@gmail.com>
2 months ago by PhillipDNrwl
Succeeded
32150
d8be48d3 cleanup(misc): fix e2e tests
2 months ago by leosvelperez
Succeeded
32155
8a77f59e Update docs/nx-cloud/reference/launch-templates.md Co-authored-by: Nicole Oliver <nicole.oliver.42@gmail.com>
2 months ago by PhillipDNrwl
Succeeded
32155
8a77f59e Update docs/nx-cloud/reference/launch-templates.md Co-authored-by: Nicole Oliver <nicole.oliver.42@gmail.com>
2 months ago by PhillipDNrwl
Failed
32150
c431a17d fix(js): add missing check for package manager workspaces
2 months ago by leosvelperez
Succeeded
32157
2be64845 fix(gradle): fix bootJar, add excludeDependsOn to false
2 months ago by xiongemi
Succeeded
32154
371aaf4c fix(release): use top-level releaseTagPattern as the default for release groups When using `nx release` with Docker projects, the `release.releaseTagPattern` defined at the root level is not inherited by docker configurations within release groups. Users must explicitly specify the `releaseTagPattern` at both the root level AND within `release.groups.<group>.docker.releaseTagPattern` for it to work correctly. Example configuration that doesn't work as expected: ```json { "release": { "releaseTagPattern": "release/{projectName}/{version}", "groups": { "apps": { "docker": { // releaseTagPattern is not inherited here } } } } } ``` The `release.releaseTagPattern` should be automatically inherited by docker configurations within release groups, following the same inheritance pattern as other release configuration properties. Users should only need to specify the pattern once at the root level unless they want to override it for specific groups. With this fix, the above configuration will work correctly, and the docker releases will use the `release/{projectName}/{version}` pattern for git tags. Fixes #29643
2 months ago by jaysoo
Failed
32157
15d4e3d2 fix(gradle): fix bootJar, add excludeDependsOn to false
2 months ago by xiongemi
Failed
32154
371aaf4c fix(release): use top-level releaseTagPattern as the default for release groups When using `nx release` with Docker projects, the `release.releaseTagPattern` defined at the root level is not inherited by docker configurations within release groups. Users must explicitly specify the `releaseTagPattern` at both the root level AND within `release.groups.<group>.docker.releaseTagPattern` for it to work correctly. Example configuration that doesn't work as expected: ```json { "release": { "releaseTagPattern": "release/{projectName}/{version}", "groups": { "apps": { "docker": { // releaseTagPattern is not inherited here } } } } } ``` The `release.releaseTagPattern` should be automatically inherited by docker configurations within release groups, following the same inheritance pattern as other release configuration properties. Users should only need to specify the pattern once at the root level unless they want to override it for specific groups. With this fix, the above configuration will work correctly, and the docker releases will use the `release/{projectName}/{version}` pattern for git tags. Fixes #29643
2 months ago by jaysoo
Canceled
32154
6cd8f94a fix(release): use top-level releaseTagPattern as the default for release groups When using `nx release` with Docker projects, the `release.releaseTagPattern` defined at the root level is not inherited by docker configurations within release groups. Users must explicitly specify the `releaseTagPattern` at both the root level AND within `release.groups.<group>.docker.releaseTagPattern` for it to work correctly. Example configuration that doesn't work as expected: ```json { "release": { "releaseTagPattern": "release/{projectName}/{version}", "groups": { "apps": { "docker": { // releaseTagPattern is not inherited here } } } } } ``` The `release.releaseTagPattern` should be automatically inherited by docker configurations within release groups, following the same inheritance pattern as other release configuration properties. Users should only need to specify the pattern once at the root level unless they want to override it for specific groups. With this fix, the above configuration will work correctly, and the docker releases will use the `release/{projectName}/{version}` pattern for git tags. Fixes #29643
2 months ago by jaysoo
Failed
32157
af95dd54 fix(gradle): fix bootJar, add excludeDependsOn to false
2 months ago by xiongemi
Canceled
32157
6b45d897 fix(gradle): fix bootJar, add excludeDependsOn to false
2 months ago by xiongemi
Failed
32155
8a77f59e Update docs/nx-cloud/reference/launch-templates.md Co-authored-by: Nicole Oliver <nicole.oliver.42@gmail.com>
2 months ago by PhillipDNrwl
Canceled
32155
8a77f59e Update docs/nx-cloud/reference/launch-templates.md Co-authored-by: Nicole Oliver <nicole.oliver.42@gmail.com>
2 months ago by PhillipDNrwl
Succeeded
32152
1c6b24c7 fix(rspack): update installed version of rspack to be same as @nx/rspack
2 months ago by ndcunningham