website/docs: manually set slug so release note URLs don't break

Signed-off-by: Jens Langhammer <jens.langhammer@beryju.org>
This commit is contained in:
Jens Langhammer 2021-04-19 21:05:19 +02:00
parent 464a1c0536
commit dc930c0cdf
10 changed files with 10 additions and 0 deletions

View file

@ -1,5 +1,6 @@
---
title: Release 0.10
slug: "0.10"
---
This update brings a lot of big features, such as:

View file

@ -1,5 +1,6 @@
---
title: Release 0.11
slug: "0.11"
---
This update brings these headline features:

View file

@ -1,5 +1,6 @@
---
title: Release 0.12
slug: "0.12"
---
This update brings these headline features:

View file

@ -1,5 +1,6 @@
---
title: Release 0.13 (passbook -> authentik)
slug: "0.13"
---
After a long back and forth, we've finally switched to a more permanent name. Whilst the upgrade is pretty much seamless, there are some things you have to change before upgrading.

View file

@ -1,5 +1,6 @@
---
title: Release 0.14
slug: "0.14"
---
## Headline features

View file

@ -1,5 +1,6 @@
---
title: Release 0.9
slug: "0.9"
---
Due to some database changes that had to be rather sooner than later, there is no possibility to directly upgrade. You must extract the data before hand and import it again. It is recommended to spin up a second instance of authentik to do this.

View file

@ -1,5 +1,6 @@
---
title: Release 2021.1
slug: "2021.1"
---
## Headline Changes

View file

@ -1,5 +1,6 @@
---
title: Release 2021.2
slug: "2021.2"
---
## Headline Changes

View file

@ -1,5 +1,6 @@
---
title: Release 2021.3
slug: "2021.3"
---
## Headline Changes

View file

@ -1,5 +1,6 @@
---
title: Release 2021.4
slug: "2021.4"
---
## Headline Changes