fix: pass parserOpts to both Bumper and ConventionalChangelog

The parserOpts parameter (including issuePrefixes) was being received
but not passed correctly to the generators. This caused custom options
configured via parserOpts to be ignored since v10.0.2.

Changes:
- Pass parserOpts as second argument to generator.commits() in the
  conventionalChangelog wrapper function
- Pass parserOpts to Bumper.commits() even when commitsOpts is not set
- Add test to verify custom issuePrefixes are applied correctly

Note: The angular preset's writer template hardcodes '#' as the issue
prefix in the output, so XYZ-123 will be parsed correctly but displayed
as release-it#123. Users who want to preserve the original prefix in output need
to customize writerOpts.

Fixes release-it#133

Author: aarond-sp

index.js

@@ -32,13 +32,8 @@ async function conventionalChangelog(
     generator.context(context);
   }
 
-  if (Object.keys(gitRawCommitsOpts).length > 0) {
-    generator.commits(gitRawCommitsOpts);
-  }
-
-  if (Object.keys(parserOpts).length > 0) {
-    // Parser options are not directly exposed in the new API
-    // They need to be passed through config or preset
+  if (Object.keys(gitRawCommitsOpts).length > 0 || Object.keys(parserOpts).length > 0) {
+    generator.commits(gitRawCommitsOpts, parserOpts);
   }
 
   if (Object.keys(writerOpts).length > 0) {
@@ -95,7 +90,9 @@ class ConventionalChangelog extends Plugin {
 
       if (options.tagOpts) bumper.tag(options.tagOpts);
 
-      if (options.commitsOpts) bumper.commits(options.commitsOpts, options.parserOpts);
+      if (options.commitsOpts || options.parserOpts) {
+        bumper.commits(options.commitsOpts || {}, options.parserOpts);
+      }
 
       let whatBumpFn;
       if (options.whatBump === false) {

test.js

@@ -451,3 +451,48 @@ test('should generate changelog with origin urls', async () => {
   const baz = commit('feat', 'baz', url);
   assert.match(nl(changelog), new RegExp('^' + title + fixes + bar + features + baz + '$'));
 });
+
+test('should apply custom issuePrefixes from parserOpts', async () => {
+  setup();
+
+  sh.exec(`git tag 1.0.0`);
+
+  // Create a commit with a custom issue reference in the body
+  sh.ShellString('bar').toEnd('bar');
+  sh.exec(`git add bar`);
+  // Use a commit with a custom issue prefix in the footer
+  sh.exec(`git commit -m "fix(bar): fix bar
+
+Refs: XYZ-123"`);
+
+  // Test 1: WITHOUT custom issuePrefixes, the parser won't recognize XYZ-123
+  // and the changelog won't show any issue reference
+  {
+    const options = getOptions({ preset });
+    const { changelog } = await runTasks(...options);
+    // Without issuePrefixes: ['XYZ-'], the parser won't detect XYZ-123 as an issue
+    // so no "closes" reference should appear
+    assert.doesNotMatch(changelog, /closes/);
+  }
+
+  // Reset and create the same commit again
+  sh.exec(`git tag 1.0.1`);
+  sh.ShellString('baz').toEnd('baz');
+  sh.exec(`git add baz`);
+  sh.exec(`git commit -m "fix(baz): fix baz
+
+Refs: XYZ-456"`);
+
+  // Test 2: WITH custom issuePrefixes, the parser recognizes XYZ-456 as an issue
+  // The angular preset outputs issues with # prefix, so we check for #456
+  {
+    const parserOpts = {
+      issuePrefixes: ['XYZ-']
+    };
+    const options = getOptions({ preset, parserOpts });
+    const { changelog } = await runTasks(...options);
+    // With issuePrefixes: ['XYZ-'], the parser detects XYZ-456 as issue 456
+    // The angular writer template outputs it as #456 (hardcoded in template)
+    assert.match(changelog, /closes.*#456/);
+  }
+});