HedgeDoc - Ideas grow better together
Alpha 2 contains many fixes. The most notable ones are
Updating from Alpha 1 to Alpha 2 should be safe. To update your setup, change the image tag for the frontend and the backend container in your docker-compose.yml to "2.0.0-alpha.2"
If you're interested in the actual commits then take a look at https://github.com/hedgedoc/hedgedoc/compare//v2.0.0-alpha.1.../v2.0.0-alpha.2
The HedgeDoc Team is proud to announce that the first alpha release of HedgeDoc 2 is now available! HedgeDoc 2 is a complete rewrite of the collaborative markdown editor, which aims to make the codebase more maintainable and adds often-requested features.
You can read more about this release in our blog post.
HedgeDoc has a new slogan! See our announcement for the details.
This release fixes a security issue. We recommend upgrading as soon as possible.
Please note: This release dropped support for Node 14, which is end-of-life since May 2023. You now need at least Node 16 to run HedgeDoc. We recommend to use the latest LTS release of Node.js.
This release switches to Yarn 3 for dependency management, as Yarn 1 has bugs preventing us from upgrading some dependencies.
If you install HedgeDoc manually, run bin/setup
again for instructions. Other installation methods should not require
special actions.
documentMaxLength
via CMD_DOCUMENT_MAX_LENGTH
environment variable (contributed by @jmallach)/status
and /metrics
endpointsbin/setup
script🚨 This release has a bug that leads to data-loss when using SQLite. We advise users of SQLite databases to skip this release and use 1.9.6. 🚨
breaks
option not being respected in the publish-viewPlease note: This release dropped support for Node 12, which is end-of-life since April 2022. You now need at least Node 14.13.1 or Node 16 to run HedgeDoc. We don't support more recent versions of Node.
This release fixes a security issue. We recommend upgrading as soon as possible.
⚠️ Warning: If you deploy HedgeDoc and MariaDB with docker-compose using a checkout of our container repo, you will need to manually convert the character set of the database to utf8mb4 when updating. See the corresponding PR for more information.
git
binary is not foundbin/manage_users
not accepting numeric passwords (thanks to @carr0t2 for reporting)