Mermaid version 10.8.0

mermaid-js · Feb 2, 2024 · f555524 · f555524
1 parent 5c9857c
commit f555524
Show file tree

Hide file tree

Showing 4 changed files with 79 additions and 21 deletions.
diff --git a/cypress/integration/rendering/block.spec.ts → cypress/integration/rendering/block.spec.js b/cypress/integration/rendering/block.spec.ts → cypress/integration/rendering/block.spec.js
diff --git a/packages/mermaid/package.json b/packages/mermaid/package.json
@@ -1,6 +1,6 @@
 {
   "name": "mermaid",
-  "version": "10.7.0",
+  "version": "10.8.0",
   "description": "Markdown-ish syntax for generating flowcharts, sequence diagrams, class diagrams, gantt charts and git graphs.",
   "type": "module",
   "module": "./dist/mermaid.core.mjs",

diff --git a/packages/mermaid/src/docs/community/contributing.md b/packages/mermaid/src/docs/community/contributing.md
@@ -371,7 +371,7 @@ If the users have no way to know that things have changed, then you haven't real
 Likewise, if users don't know that there is a new feature that you've implemented, it will forever remain unknown and unused.
 
 The documentation has to be updated for users to know that things have been changed and added!
-If you are adding a new feature, add `(v<MERMAID_RELEASE_VERSION>+)` in the title or description. It will be replaced automatically with the current version number when the release happens.
+If you are adding a new feature, add `(v10.8.0+)` in the title or description. It will be replaced automatically with the current version number when the release happens.
 
 eg: `# Feature Name (v<MERMAID_RELEASE_VERSION>+)`
 

diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml