fix(generate-notes): use release-notes-generator plugin

Otherwise, both release notes are concatenated together.

BREAKING CHANGE: users should now remove release-notes-generator
from their plugin list.

README.md

@@ -36,7 +36,6 @@ $ yarn add --dev semantic-release-jira-notes
 {
   "plugins": [
     "@semantic-release/commit-analyzer",
-    "@semantic-release/release-notes-generator",
     ["semantic-release-jira-notes", {
       "jiraHost": "iamludal.atlassian.net",
       "ticketPrefixes": ["ATP", "OMS"]
@@ -47,6 +46,4 @@ $ yarn add --dev semantic-release-jira-notes
 }
 ```
 
-> **Note:** don't forget to use `@semantic-release/release-notes-generator` before, as it will generate
-the release notes needed for `semantic-release-jira-notes`.
-
+> **Note:** you don't need to use `@semantic-release/release-notes-generator`.

package.json

@@ -15,6 +15,7 @@
   ],
   "dependencies": {
     "@semantic-release/error": "2.2.0",
+    "@semantic-release/release-notes-generator": "^10.0.3",
     "aggregate-error": "^4.0.1"
   }
 }

src/lib/generate-notes.js

@@ -1,8 +1,10 @@
 const { INPUTS, ISSUE_REGEX } = require("./constants");
+const { generateNotes } = require("@semantic-release/release-notes-generator");
 
-module.exports = async (pluginConfig, { nextRelease: { notes } }) => {
+module.exports = async (pluginConfig, context) => {
   const ticketPrefixes = pluginConfig[INPUTS.ticketPrefixes];
   const jiraHost = pluginConfig[INPUTS.jiraHost];
+  const notes = await generateNotes(pluginConfig, context);
 
   let issueRegex;