Fix for handling new version where only a subset of docs contents are…

… different

The previous commit would fix the borken relative links involving `--skip-next-release` when
the very first/initial version is created or if **all** docs were updated before creating a
version. If only a few/one doc was updated before creating a version, there would still be
broken relative links when building the site with `--skip-next-release` docs.

This commit fixes the issues mentioned above.

packages/docusaurus-1.x/lib/server/docs.js

@@ -69,9 +69,19 @@ function mdToHtmlify(oldContent, mdToHtml, metadata, siteConfig) {
     let mdMatch = mdRegex.exec(modifiedLine);
     while (mdMatch !== null) {
       /* Replace it to correct html link */
-      const docsSource = metadata.source;
+      let docsSource;
+      if (readMetadata.shouldGenerateNextReleaseDocs()) {
+        docsSource = metadata.version
+          ? metadata.source.replace(/version-.*?\//, '')
+          : metadata.source;
+      } else {
+        docsSource = metadata.source;
+      }
       let htmlLink =
-        mdToHtml[resolve(docsSource, mdMatch[1])] || mdToHtml[mdMatch[1]];
+        mdToHtml[resolve(docsSource, mdMatch[1])] ||
+        mdToHtml[mdMatch[1]] ||
+        resolve(docsSource, mdMatch[1]).replace('.md', '.html');
+
       if (htmlLink) {
         htmlLink = getPath(htmlLink, siteConfig.cleanUrl);
         htmlLink = htmlLink.replace('/en/', `/${metadata.language}/`);

packages/docusaurus-1.x/lib/server/readMetadata.js

@@ -404,4 +404,5 @@ module.exports = {
   processMetadata,
   generateMetadataDocs,
   generateMetadataBlog,
+  shouldGenerateNextReleaseDocs,
 };