Overview - Nx

Nx

7 days30 days

Latest CI Pipeline Executions

Exact

Succeeded
154
374abf9a
9 days ago
u
Succeeded
154
fffbd72f
12 days ago
u
Succeeded
31542
ba9deb49 fix(expo): update heading text assertion to use regex for flexibility
21 days ago by gilhanan
Succeeded
154
1b8bae7d
25 days ago
u
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
1 month ago by jaysoo
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
1 month 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
1 month ago by jaysoo
Failed
32154
916c6edb 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
1 month ago by jaysoo
Failed
32154
5e4be234 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
1 month ago by jaysoo
Canceled
32154
99dfe958 fix(release): use top-level releaseTagPattern as the default for release groups ## Current Behavior 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 } } } } } ``` ## Expected Behavior 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. ## Related Issue(s) Fixes #29643
1 month ago by jaysoo
Succeeded
31545
6a8e2421 fix(js): ignore versioning as technique to find workspace modules
3 months ago by Coly010
Canceled
31545
a42b2743 fix(js): ignore versioning as technique to find workspace modules
3 months ago by Coly010
Failed
31545
07f54141 fix(js): handle case where workspace module cannot be found Co-authored-by: graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com>
3 months ago by Coly010
Succeeded
31545
fc6ffdd9 fix(js): handle case where workspace module cannot be found Co-authored-by: graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com>
3 months ago by Coly010
Failed
31545
71606865 fix(js): handle case where workspace module cannot be found Co-authored-by: graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com>
3 months ago by Coly010
Succeeded
31545
01e42498 chore(js): fixup e2es
3 months ago by Coly010
Failed
31545
75fdcb4c chore(js): update e2e
3 months ago by Coly010
Succeeded
31548
c9fbb2d2 docs(nx-dev): add 21.2 release article
3 months ago by philipjful...
Succeeded
31548
03ae542d docs(nx-dev): add 21.2 release article
3 months ago by philipjful...
Canceled
31548
8a372071 docs(devkit): fix instructions for creating sync generators (#31576) Co-authored-by: Caleb Ukle <caleb@nrwl.io>
3 months ago by juristr