Support MERMAID_RELEASE_VERSION in docs

This commit is contained in:
Sidharth Vinod
2023-07-07 11:28:04 +05:30
parent 194ef202ac
commit 88856a721f
6 changed files with 59 additions and 19 deletions

View File

@@ -212,6 +212,9 @@ 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 to users know that things have 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.
eg: `# Feature Name (v<MERMAID_RELEASE_VERSION>+)`
We know it can sometimes be hard to code _and_ write user documentation.