Overview - Nx

Nx

7 days30 days

Latest CI Pipeline Executions

Exact

Succeeded
master
1089ffc4 fix(docker): guard commitSha null in plugin interpolation (#33275) ## Current Behavior Docker plugin assumed `commitSha` was always non-null; when `null`, `shortCommitSha.slice` caused a runtime error during target interpolation. ## Expected Behavior Plugin should succeed even if latest commit SHA cannot be resolved, simply omitting shortCommitSha-based substitutions. ## Changes - Added null guard: `shortCommitSha` now set to `commitSha ? commitSha.slice(0,7) : null`. - Added test "should not throw when commitSha is null" verifying node / target creation succeeds. - No breaking changes; only broadens safe input surface. ## Additional notes Logic only executes when `commitSha` was previously null (error case); normal paths unchanged. If consumers interpolate `{shortCommitSha}`, they should handle possible null (unchanged if interpolation is already optional).
8 hours ago by emiliosheinz
Succeeded
master
1089ffc4 fix(docker): guard commitSha null in plugin interpolation (#33275) ## Current Behavior Docker plugin assumed `commitSha` was always non-null; when `null`, `shortCommitSha.slice` caused a runtime error during target interpolation. ## Expected Behavior Plugin should succeed even if latest commit SHA cannot be resolved, simply omitting shortCommitSha-based substitutions. ## Changes - Added null guard: `shortCommitSha` now set to `commitSha ? commitSha.slice(0,7) : null`. - Added test "should not throw when commitSha is null" verifying node / target creation succeeds. - No breaking changes; only broadens safe input surface. ## Additional notes Logic only executes when `commitSha` was previously null (error case); normal paths unchanged. If consumers interpolate `{shortCommitSha}`, they should handle possible null (unchanged if interpolation is already optional).
12 hours ago by emiliosheinz
Succeeded
master
1089ffc4 fix(docker): guard commitSha null in plugin interpolation (#33275) ## Current Behavior Docker plugin assumed `commitSha` was always non-null; when `null`, `shortCommitSha.slice` caused a runtime error during target interpolation. ## Expected Behavior Plugin should succeed even if latest commit SHA cannot be resolved, simply omitting shortCommitSha-based substitutions. ## Changes - Added null guard: `shortCommitSha` now set to `commitSha ? commitSha.slice(0,7) : null`. - Added test "should not throw when commitSha is null" verifying node / target creation succeeds. - No breaking changes; only broadens safe input surface. ## Additional notes Logic only executes when `commitSha` was previously null (error case); normal paths unchanged. If consumers interpolate `{shortCommitSha}`, they should handle possible null (unchanged if interpolation is already optional).
14 hours ago by emiliosheinz
Succeeded
master
1089ffc4 fix(docker): guard commitSha null in plugin interpolation (#33275) ## Current Behavior Docker plugin assumed `commitSha` was always non-null; when `null`, `shortCommitSha.slice` caused a runtime error during target interpolation. ## Expected Behavior Plugin should succeed even if latest commit SHA cannot be resolved, simply omitting shortCommitSha-based substitutions. ## Changes - Added null guard: `shortCommitSha` now set to `commitSha ? commitSha.slice(0,7) : null`. - Added test "should not throw when commitSha is null" verifying node / target creation succeeds. - No breaking changes; only broadens safe input surface. ## Additional notes Logic only executes when `commitSha` was previously null (error case); normal paths unchanged. If consumers interpolate `{shortCommitSha}`, they should handle possible null (unchanged if interpolation is already optional).
15 hours ago by emiliosheinz
Succeeded
33275
f9dff932 fix(docker): guard commitSha null in plugin interpolation
21 hours ago by emiliosheinz
Failed
master
b2ba8c27 feat(release): support {versionActionsVersion} in docker version scheme (#33178)
6 days ago by emiliosheinz
Succeeded
master
b2ba8c27 feat(release): support {versionActionsVersion} in docker version scheme (#33178)
6 days ago by emiliosheinz
Succeeded
33178
2179c4c2 feat(release): support {versionActionsVersion} in docker version scheme This commit adds support for using {versionActionsVersion} in the Docker version scheme. When interpolated, it will be automatically replaced with the version your project is being bumped to. This ensures that your package.json, tags, changelog, releases, and Docker image versions remain consistent and aligned. Closes #33131
6 days ago by emiliosheinz
Failed
33178
2179c4c2 feat(release): support {versionActionsVersion} in docker version scheme This commit adds support for using {versionActionsVersion} in the Docker version scheme. When interpolated, it will be automatically replaced with the version your project is being bumped to. This ensures that your package.json, tags, changelog, releases, and Docker image versions remain consistent and aligned. Closes #33131
6 days ago by emiliosheinz
Failed
33178
8ce3679a feat(release): support {versionActionsVersion} in docker version scheme This commit adds support for using {versionActionsVersion} in the Docker version scheme. When interpolated, it will be automatically replaced with the version your project is being bumped to. This ensures that your package.json, tags, changelog, releases, and Docker image versions remain consistent and aligned. Closes #33131
6 days ago by emiliosheinz
Succeeded
33178
30277a8c feat(release): support {versionActionsVersion} in docker version scheme This commit adds support for using {versionActionsVersion} in the Docker version scheme. When interpolated, it will be automatically replaced with the version your project is being bumped to. This ensures that your package.json, tags, changelog, releases, and Docker image versions remain consistent and aligned. Closes #33131
7 days ago by emiliosheinz