Open fralau opened 1 year ago
One solution could be to get the latest release from github (see how to do this in Python).
Put it could be that the simplest option is to update the library version number as we go.
So far, it seems that updating progressively the reference version of mermaid.js is still the best thing. This gives a better guarantee that the Mkdocs-Mermaid2 package will continue to work. In any case, it is possible to change the javascript library's version with the version
parameter in the config file; or even (new in 1.1.0) to provide the URL.
Currently, mkdocs-mermaid2 seems to take by default the MERMAID_LIB_VERSION.
We could also use an approach where it takes the latest version of the mermaid library by default.
It happened once in the past, that the latest version was problematic, and it broke the build. Which is why we wanted to keep control on the 'recommended' (stable) version
We could have a compromise solution?