Overview - Nx

Nx

7 days30 days

Latest CI Pipeline Executions

Failed
33779
25e4f3b0 fix(release): {releaseGroupName} not interpolated in changelog tag/release name
15 hours ago by jogelin
Failed
33779
Fix applied→
d2d87c38 fix(release): {releaseGroupName} not interpolated in changelog tag/release name
17 hours ago by jogelin
Succeeded
master
8207c946 feat(docker): auto-select version scheme when only one is available (#33671)
8 days ago by jogelin
Succeeded
master
4923c15e fix(release): interpolate releaseGroupName in getLatestGitTagForPattern (#33674) # Fix: Pass releaseGroupName to getLatestGitTagForPattern for proper tag resolution ## Problem When using `releaseTag.pattern: "{releaseGroupName}@{version}"`, Nx fails to resolve versions from git tags because the `{releaseGroupName}` placeholder is not interpolated. For example, with git tag `my-group@2.9.0`: - **Expected**: Extract version `2.9.0` - **Actual**: Extracts `"my-group"` → Error: `Invalid semver version 'my-group' provided` ## Root Cause In `release-graph.ts:627-631`, only `projectName` is passed to `getLatestGitTagForPattern()`, missing `releaseGroupName` needed for interpolation. ## Solution Pass `releaseGroupName` to the interpolation data (1-line change at `release-graph.ts:631`): ```typescript latestMatchingGitTag = await getLatestGitTagForPattern( releaseTagPattern, { projectName: projectGraphNode.name, releaseGroupName: releaseGroupNode.group.name, // ✅ Added }, { ... } ); ``` ## Backward Compatibility ✅ Fully backward compatible: - `releaseGroupNode.group.name` is always defined (user-defined or `"__default__"`) - Unused interpolation data is safely ignored - Existing patterns (`v{version}`, `{projectName}@{version}`) continue to work ## Tests Added test case in `git.spec.ts` for `{releaseGroupName}@{version}` pattern that verifies correct tag matching and version extraction. ## Files Changed - `packages/nx/src/command-line/release/utils/release-graph.ts` (1 line) - `packages/nx/src/command-line/release/utils/git.spec.ts` (1 test case) Co-authored-by: James Henry <james@henry.sc>
8 days ago by jogelin
Succeeded
master
8207c946 feat(docker): auto-select version scheme when only one is available (#33671)
9 days ago by jogelin
Succeeded
master
4923c15e fix(release): interpolate releaseGroupName in getLatestGitTagForPattern (#33674) # Fix: Pass releaseGroupName to getLatestGitTagForPattern for proper tag resolution ## Problem When using `releaseTag.pattern: "{releaseGroupName}@{version}"`, Nx fails to resolve versions from git tags because the `{releaseGroupName}` placeholder is not interpolated. For example, with git tag `my-group@2.9.0`: - **Expected**: Extract version `2.9.0` - **Actual**: Extracts `"my-group"` → Error: `Invalid semver version 'my-group' provided` ## Root Cause In `release-graph.ts:627-631`, only `projectName` is passed to `getLatestGitTagForPattern()`, missing `releaseGroupName` needed for interpolation. ## Solution Pass `releaseGroupName` to the interpolation data (1-line change at `release-graph.ts:631`): ```typescript latestMatchingGitTag = await getLatestGitTagForPattern( releaseTagPattern, { projectName: projectGraphNode.name, releaseGroupName: releaseGroupNode.group.name, // ✅ Added }, { ... } ); ``` ## Backward Compatibility ✅ Fully backward compatible: - `releaseGroupNode.group.name` is always defined (user-defined or `"__default__"`) - Unused interpolation data is safely ignored - Existing patterns (`v{version}`, `{projectName}@{version}`) continue to work ## Tests Added test case in `git.spec.ts` for `{releaseGroupName}@{version}` pattern that verifies correct tag matching and version extraction. ## Files Changed - `packages/nx/src/command-line/release/utils/release-graph.ts` (1 line) - `packages/nx/src/command-line/release/utils/git.spec.ts` (1 test case) Co-authored-by: James Henry <james@henry.sc>
9 days ago by jogelin
Succeeded
master
4923c15e fix(release): interpolate releaseGroupName in getLatestGitTagForPattern (#33674) # Fix: Pass releaseGroupName to getLatestGitTagForPattern for proper tag resolution ## Problem When using `releaseTag.pattern: "{releaseGroupName}@{version}"`, Nx fails to resolve versions from git tags because the `{releaseGroupName}` placeholder is not interpolated. For example, with git tag `my-group@2.9.0`: - **Expected**: Extract version `2.9.0` - **Actual**: Extracts `"my-group"` → Error: `Invalid semver version 'my-group' provided` ## Root Cause In `release-graph.ts:627-631`, only `projectName` is passed to `getLatestGitTagForPattern()`, missing `releaseGroupName` needed for interpolation. ## Solution Pass `releaseGroupName` to the interpolation data (1-line change at `release-graph.ts:631`): ```typescript latestMatchingGitTag = await getLatestGitTagForPattern( releaseTagPattern, { projectName: projectGraphNode.name, releaseGroupName: releaseGroupNode.group.name, // ✅ Added }, { ... } ); ``` ## Backward Compatibility ✅ Fully backward compatible: - `releaseGroupNode.group.name` is always defined (user-defined or `"__default__"`) - Unused interpolation data is safely ignored - Existing patterns (`v{version}`, `{projectName}@{version}`) continue to work ## Tests Added test case in `git.spec.ts` for `{releaseGroupName}@{version}` pattern that verifies correct tag matching and version extraction. ## Files Changed - `packages/nx/src/command-line/release/utils/release-graph.ts` (1 line) - `packages/nx/src/command-line/release/utils/git.spec.ts` (1 test case) Co-authored-by: James Henry <james@henry.sc>
9 days ago by jogelin
Succeeded
master
4923c15e fix(release): interpolate releaseGroupName in getLatestGitTagForPattern (#33674) # Fix: Pass releaseGroupName to getLatestGitTagForPattern for proper tag resolution ## Problem When using `releaseTag.pattern: "{releaseGroupName}@{version}"`, Nx fails to resolve versions from git tags because the `{releaseGroupName}` placeholder is not interpolated. For example, with git tag `my-group@2.9.0`: - **Expected**: Extract version `2.9.0` - **Actual**: Extracts `"my-group"` → Error: `Invalid semver version 'my-group' provided` ## Root Cause In `release-graph.ts:627-631`, only `projectName` is passed to `getLatestGitTagForPattern()`, missing `releaseGroupName` needed for interpolation. ## Solution Pass `releaseGroupName` to the interpolation data (1-line change at `release-graph.ts:631`): ```typescript latestMatchingGitTag = await getLatestGitTagForPattern( releaseTagPattern, { projectName: projectGraphNode.name, releaseGroupName: releaseGroupNode.group.name, // ✅ Added }, { ... } ); ``` ## Backward Compatibility ✅ Fully backward compatible: - `releaseGroupNode.group.name` is always defined (user-defined or `"__default__"`) - Unused interpolation data is safely ignored - Existing patterns (`v{version}`, `{projectName}@{version}`) continue to work ## Tests Added test case in `git.spec.ts` for `{releaseGroupName}@{version}` pattern that verifies correct tag matching and version extraction. ## Files Changed - `packages/nx/src/command-line/release/utils/release-graph.ts` (1 line) - `packages/nx/src/command-line/release/utils/git.spec.ts` (1 test case) Co-authored-by: James Henry <james@henry.sc>
9 days ago by jogelin
Canceled
master
4923c15e fix(release): interpolate releaseGroupName in getLatestGitTagForPattern (#33674) # Fix: Pass releaseGroupName to getLatestGitTagForPattern for proper tag resolution ## Problem When using `releaseTag.pattern: "{releaseGroupName}@{version}"`, Nx fails to resolve versions from git tags because the `{releaseGroupName}` placeholder is not interpolated. For example, with git tag `my-group@2.9.0`: - **Expected**: Extract version `2.9.0` - **Actual**: Extracts `"my-group"` → Error: `Invalid semver version 'my-group' provided` ## Root Cause In `release-graph.ts:627-631`, only `projectName` is passed to `getLatestGitTagForPattern()`, missing `releaseGroupName` needed for interpolation. ## Solution Pass `releaseGroupName` to the interpolation data (1-line change at `release-graph.ts:631`): ```typescript latestMatchingGitTag = await getLatestGitTagForPattern( releaseTagPattern, { projectName: projectGraphNode.name, releaseGroupName: releaseGroupNode.group.name, // ✅ Added }, { ... } ); ``` ## Backward Compatibility ✅ Fully backward compatible: - `releaseGroupNode.group.name` is always defined (user-defined or `"__default__"`) - Unused interpolation data is safely ignored - Existing patterns (`v{version}`, `{projectName}@{version}`) continue to work ## Tests Added test case in `git.spec.ts` for `{releaseGroupName}@{version}` pattern that verifies correct tag matching and version extraction. ## Files Changed - `packages/nx/src/command-line/release/utils/release-graph.ts` (1 line) - `packages/nx/src/command-line/release/utils/git.spec.ts` (1 test case) Co-authored-by: James Henry <james@henry.sc>
9 days ago by jogelin
Canceled
master
8207c946 feat(docker): auto-select version scheme when only one is available (#33671)
9 days ago by jogelin
Succeeded
master
8207c946 feat(docker): auto-select version scheme when only one is available (#33671)
9 days ago by jogelin
Failed
master
8207c946 feat(docker): auto-select version scheme when only one is available (#33671)
9 days ago by jogelin
Canceled
master
8207c946 feat(docker): auto-select version scheme when only one is available (#33671)
9 days ago by jogelin
Succeeded
master
a4c13212 fix(docker): fix releasing non docker projects (#33667)
9 days ago by jogelin
Canceled
33674
330858af fix(release): pass releaseGroupName to getLatestGitTagForPattern for proper tag resolution
9 days ago by jogelin
Succeeded
33671
62aac7ff feat(docker): auto-select version scheme when only one is available
10 days ago by jogelin
Succeeded
33667
594db50b fix(docker): fix releasing non docker projects
10 days ago by jogelin
Failed
33667
594db50b fix(docker): fix releasing non docker projects
10 days ago by jogelin
Succeeded
master
5ea2e47a fix(core): display prettier valid errors (#32771)      ## Current Behavior When running `nx format:check`, if there is an error, it is considered as files not formatted correctly But if Prettier is throwing a real error, it is not diplayed. We just see an empty result without information For example: Format check failing with empty result ``` nx format:check ``` But when running the command, we can see the error: ``` node "/node_modules/prettier/bin/prettier.cjs" --list-different "packages/lib/.spec.swcrc" packages/lib/.spec.swcrc [error] No parser could be inferred for file "/packages/lib/.spec.swcrc". ``` ## Expected Behavior I should see the prettier error to understand why it is failing ## Related Issue(s)  Fixes #
3 months ago by jogelin
Succeeded
master
5ea2e47a fix(core): display prettier valid errors (#32771)      ## Current Behavior When running `nx format:check`, if there is an error, it is considered as files not formatted correctly But if Prettier is throwing a real error, it is not diplayed. We just see an empty result without information For example: Format check failing with empty result ``` nx format:check ``` But when running the command, we can see the error: ``` node "/node_modules/prettier/bin/prettier.cjs" --list-different "packages/lib/.spec.swcrc" packages/lib/.spec.swcrc [error] No parser could be inferred for file "/packages/lib/.spec.swcrc". ``` ## Expected Behavior I should see the prettier error to understand why it is failing ## Related Issue(s)  Fixes #
3 months ago by jogelin