PR Description

Related: #33674

Problem

The {releaseGroupName} placeholder in releaseTag.pattern was never interpolated. Instead, it appeared URL-encoded in generated git tags, release URLs, and commit messages.

Example

release: {
  groups: {
    my-group: { ... }
  },
  releaseTag: {
    pattern: '{releaseGroupName}@{version}'
  }
}

Expected:
my-group@22.6.0

Actual:
%7BreleaseGroupName%7D%4022.6.0

This affected:

• Release URLs (GitHub/GitLab)
• Git tag names
• Commit messages referencing tags

Root Cause

releaseGroupName was never passed through the release pipeline. The ReleaseVersion class and related helper functions accepted {projectName} and {version}, but not {releaseGroupName}, causing the placeholder to remain unprocessed.

Solution

Support for releaseGroupName has now been added throughout the release flow:

1. Updated ReleaseVersion to accept and interpolate releaseGroupName.
2. Updated workspace changelog to extract the group name from nxReleaseConfig.groups.
3. Updated project changelog to pass releaseGroup.name.
4. Updated commit message generation to include releaseGroupName in all ReleaseVersion instances.
5. Updated git tag creation for both fixed and independent groups to pass releaseGroupName.

Changes by File

packages/nx/src/command-line/release/utils/shared.ts

• Added releaseGroupName to ReleaseVersion constructor.
• Passed releaseGroupName in createCommitMessageValues().
• Passed releaseGroupName in createGitTagValues() for fixed and independent groups.

packages/nx/src/command-line/release/changelog.ts

• Workspace changelog: infer group name using Object.keys(nxReleaseConfig.groups)[0].
• Project changelog: pass releaseGroup.name to interpolation.

packages/nx/src/command-line/release/utils/shared.spec.ts

• Added tests for fixed groups and independent groups to ensure {releaseGroupName} interpolates correctly.

Testing

New tests

• Fixed groups

  • Pattern: {releaseGroupName}@{version}
  • Output: forge@1.1.0

• Independent groups

  • Pattern: {releaseGroupName}/{projectName}@{version}
  • Output: my-group/a@1.1.0, my-group/b@1.2.0

Manual Verification

Before:

https://gitlab.example.com/repo/-/releases/%7BreleaseGroupName%7D%4022.6.0

After:

https://gitlab.example.com/repo/-/releases/my-group@22.6.0

Backward Compatibility

No breaking changes:

• releaseGroupName is optional.
• Configurations not using {releaseGroupName} behave as before.
• All existing tests continue to pass.
• The change is additive and consistent with existing interpolation logic.