Overview - Nx

Nx

7 days30 days

Latest CI Pipeline Executions

Exact

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