Bump version to 1.9.8

Signed-off-by: David Mehren <git@herrmehren.de>
This commit is contained in:
David Mehren 2023-06-04 19:33:04 +02:00
parent 689ca2018d
commit 57c2865224
5 changed files with 10 additions and 10 deletions

View file

@ -3,7 +3,7 @@ openapi: 3.0.1
info:
title: HedgeDoc
description: HedgeDoc is an open source collaborative note editor. Several tasks of HedgeDoc can be automated through this API.
version: 1.9.7
version: 1.9.8
contact:
name: HedgeDoc on GitHub
url: https://github.com/hedgedoc/hedgedoc

View file

@ -28,7 +28,7 @@ services:
restart: always
app:
# Make sure to use the latest release from https://hedgedoc.org/latest-release
image: quay.io/hedgedoc/hedgedoc:1.9.7
image: quay.io/hedgedoc/hedgedoc:1.9.8
environment:
- CMD_DB_URL=postgres://hedgedoc:password@database:5432/hedgedoc
- CMD_DOMAIN=localhost

View file

@ -19,7 +19,7 @@
1. Check if you meet the [requirements at the top of this document](#manual-installation).
2. Download the [latest release](https://hedgedoc.org/latest-release/) and extract it.
<small>Alternatively, you can use Git to clone the repository and checkout a release, e.g. with `git clone -b 1.9.7 https://github.com/hedgedoc/hedgedoc.git`.</small>
<small>Alternatively, you can use Git to clone the repository and checkout a release, e.g. with `git clone -b 1.9.8 https://github.com/hedgedoc/hedgedoc.git`.</small>
3. Enter the directory and execute `bin/setup`, which will install the dependencies and create example configs.
4. Configure HedgeDoc: To get started, you can use this minimal `config.json`:
```json
@ -61,7 +61,7 @@ If you want to upgrade HedgeDoc from an older version, follow these steps:
and the latest release.
2. Fully stop your old HedgeDoc server.
3. [Download](https://hedgedoc.org/latest-release/) the new release and extract it over the old directory.
<small>If you use Git, you can check out the new tag with e.g. `git fetch origin && git checkout 1.9.7`</small>
<small>If you use Git, you can check out the new tag with e.g. `git fetch origin && git checkout 1.9.8`</small>
5. Run `bin/setup`. This will take care of installing dependencies. It is safe to run on an existing installation.
6. *:octicons-light-bulb-16: If you used the release tarball for 1.7.0 or newer, this step can be skipped.*
Build the frontend bundle by running `yarn install --immutable` and `yarn build`. The extra `yarn install --immutable` is necessary as `bin/setup` does not install the build dependencies.

View file

@ -1,6 +1,6 @@
{
"name": "HedgeDoc",
"version": "1.9.7",
"version": "1.9.8",
"description": "The best platform to write and share markdown.",
"main": "app.js",
"license": "AGPL-3.0",

View file

@ -1,6 +1,6 @@
# Release Notes
## UNRELEASED
## <i class="fa fa-tag"></i> 1.9.8 <i class="fa fa-calendar-o"></i> 2023-06-04
**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.
@ -10,15 +10,15 @@ If you install HedgeDoc manually, run `bin/setup` again for instructions. Other
special actions.
### Enhancements
- Extend boolean environment variable parsing with other positive answers and case insensitivity.
- Allow setting of `documentMaxLength` via `CMD_DOCUMENT_MAX_LENGTH` environment variable.
- Add dedicated healthcheck endpoint at /_health that is less resource intensive than /status.
- Extend boolean environment variable parsing with other positive answers and case insensitivity
- Allow setting of `documentMaxLength` via `CMD_DOCUMENT_MAX_LENGTH` environment variable (contributed by [@jmallach](https://github.com/jmallach))
- Add dedicated healthcheck endpoint at /_health that is less resource intensive than /status
- Compatibility with Node.js 18 and later
- Add support for the arm64 architecture in the docker image
- Add a config option to disable the `/status` and `/metrics` endpoints
### Bugfixes
- Fix that permission errors can break existing connections to a note, causing inconsistent note content and changes not being saved
- Fix that permission errors can break existing connections to a note, causing inconsistent note content and changes not being saved (contributed by [@julianrother](https://github.com/julianrother))
- Fix speaker notes not showing up in the presentation view
- Fix issues with upgrading some dependencies by upgrading to Yarn 3
- Fix macOS compatibility of `bin/setup` script