docs: add clarifications for this change

Author: Leundai

docs/customizing.md

@@ -116,6 +116,35 @@ If you wish to avoid that, consider using `component-no-space: true`/`--componen
 | `${version}` | The version of the component being released |
 | `${branch?}` | The target branch of the pull request. If you have multiple release branches, this helps identify which release branch we are working on |
 
+#### Group Pull Request Title
+
+For grouped/merged pull requests (when using plugins like `linked-versions` or when `separate-pull-requests` is `false`), you can use the `group-pull-request-title-pattern` option instead:
+
+```json
+{
+  "group-pull-request-title-pattern": "chore${scope}: release ${component} ${version}"
+}
+```
+
+This pattern uses the same placeholders as `pull-request-title-pattern`. When used with the `linked-versions` plugin, the `${component}` placeholder will be replaced with the plugin's `groupName`.
+
+For example, with the configuration:
+
+```json
+{
+  "group-pull-request-title-pattern": "chore${scope}: release ${component} ${version}",
+  "plugins": [
+    {
+      "type": "linked-versions",
+      "groupName": "my-sdk",
+      "components": ["pkgA", "pkgB"]
+    }
+  ]
+}
+```
+
+The resulting pull request title will be: `chore(main): release my-sdk v1.2.3`
+
 ### Pull Request Header
 
 If you would like to customize the pull request header, you can use the

docs/manifest-releaser.md

@@ -235,6 +235,8 @@ defaults (those are documented in comments)
   // Template values (i.e. ${scope}, ${component} and ${version}) are inherited
   // from the root path's (i.e. '.') package, if present
   // absence defaults to "chore: release ${branch}"
+  // Note: When used with the `linked-versions` plugin, ${component} will be
+  // replaced with the plugin's groupName.
   "group-pull-request-title-pattern": "chore: release ${branch}",
 
   // When searching for the latest release SHAs, only consider the last N releases.
@@ -568,7 +570,49 @@ Note: when combining the `linked-versions` plugin with a `workspace` plugin,
 you will need to tell the `workspace` plugin to skip its own internal merge.
 See #1457 for context.
 
-Example:
+#### Pull Request Title Configuration
+
+By default, the `linked-versions` plugin generates pull request titles with
+the format `chore(scope): release <groupName> libraries`. You can customize
+this by using the `group-pull-request-title-pattern` option:
+
+```json
+{
+  "release-type": "rust",
+  "group-pull-request-title-pattern": "chore${scope}: release ${component} ${version}",
+  "packages": {
+    "packages/rustA": {
+      "component": "pkgA"
+    },
+    "packages/rustB": {
+      "component": "pkgB"
+    }
+  },
+  "plugins": [
+    {
+      "type": "cargo-workspace",
+      "merge": false
+    },
+    {
+      "type": "linked-versions",
+      "groupName": "my-sdk",
+      "components": [
+        "pkgA", "pkgB"
+      ]
+    }
+  ]
+}
+```
+
+With this configuration, the pull request title will be
+`chore(main): release my-sdk v1.2.3` instead of the default
+`chore(main): release my-sdk libraries`.
+
+The `${component}` placeholder in the pattern will be replaced with the
+`groupName` from the plugin configuration. Other available placeholders are
+`${scope}`, `${version}`, and `${branch}`.
+
+Example without configuration (backward compatibility):
 
 ```json
 {
@@ -597,6 +641,8 @@ Example:
 }
 ```
 
+This will use the default title: `chore(main): release my group libraries`.
+
 ### sentence-case
 
 Capitalize the leading word in a commit message, taking into account common exceptions, e.g., gRPC.