self-hosted GitLab - no issue links in release notes

[chopeen]

I have a CI pipeline with semantic-release configured and it is working as expected, expect for lack of issue links in the generated release notes.

Here's the debug output - what baffles me is the host appearing twice, with different values!

Which setting is it?
Is it a setting of conventional-changelog (discussed here) or is it a setting of release-notes-generator?

[9:42:34 AM] [semantic-release] › ℹ  Start step "generateNotes" of plugin "@semantic-release/release-notes-generator"
2024-01-03T09:42:34.862Z semantic-release:release-notes-generator version: '1.0.4'
2024-01-03T09:42:34.863Z semantic-release:release-notes-generator host: undefined
2024-01-03T09:42:34.863Z semantic-release:release-notes-generator owner: 'foorbar'
2024-01-03T09:42:34.863Z semantic-release:release-notes-generator repository: 'semantic-release-example'
2024-01-03T09:42:34.863Z semantic-release:release-notes-generator previousTag: '1.0.3'
2024-01-03T09:42:34.863Z semantic-release:release-notes-generator currentTag: '1.0.4'
2024-01-03T09:42:34.863Z semantic-release:release-notes-generator host: 'https://my.instance.com'
2024-01-03T09:42:34.863Z semantic-release:release-notes-generator linkReferences: true
2024-01-03T09:42:34.863Z semantic-release:release-notes-generator issue: 'issues'
2024-01-03T09:42:34.863Z semantic-release:release-notes-generator commit: 'commit'
[9:42:34 AM] [semantic-release] › ✔  Completed step "generateNotes" of plugin "@semantic-release/release-notes-generator"
[9:42:36 AM] [semantic-release] › ✔  Created tag 1.0.4
[9:42:36 AM] [semantic-release] › ℹ  Start step "publish" of plugin "@semantic-release/gitlab"
2024-01-03T09:42:36.942Z semantic-release:gitlab repoId: 'foorbar/semantic-release-example'
2024-01-03T09:42:36.942Z semantic-release:gitlab release name: '1.0.4'
2024-01-03T09:42:36.942Z semantic-release:gitlab release ref: '042dcfbdcba97ba06a90d5990fc6e73938e6a4d6'
2024-01-03T09:42:36.942Z semantic-release:gitlab milestones: undefined
2024-01-03T09:42:36.942Z semantic-release:gitlab Create a release for git tag '1.0.4' with commit '042dcfbdcba97ba06a90d5990fc6e73938e6a4d6'
2024-01-03T09:42:36.942Z semantic-release:gitlab POST-ing the following JSON to https://my.instance.com/api/v4/projects/foorbar%2Fsemantic-release-example/releases:
{
  "tag_name": "1.0.4",
  "description": "## [1.0.4](https://my.instance.com/foorbar/semantic-release-example/compare/1.0.3...1.0.4) (2024-01-03)\n\n\n### Bug Fixes\n\n* Try writerOpts ([713837c](https://my.instance.com/foorbar/semantic-release-example/commit/713837c11e190003e40f54a173f687bfffc8f5fb))\n\n",
  "assets": {
    "links": []
  }
}

For a self-hosted GitLab instance, what options should I set to have issue links in the generated release notes?

[W1M0R]

I am experiencing this exact same issue. Do you perhaps have any insights on this issue @travi?