diff --git a/.forgejo/workflows/build.yaml b/.forgejo/workflows/build.yaml
index 6bf9c43..8899e1d 100644
--- a/.forgejo/workflows/build.yaml
+++ b/.forgejo/workflows/build.yaml
@@ -2,6 +2,8 @@
 # SPDX-License-Identifier: AGPL-3.0-or-later
 on:
   push:
+    branches:
+      - develop
 env:
   REGISTRY_IMAGE: ${{ vars.REGISTRY }}/${{ github.repository }}:${{ github.ref_name }}
 
diff --git a/docs/admin/authentication.md b/docs/admin/authentication.md
index 98971b0..a1fbc3e 100644
--- a/docs/admin/authentication.md
+++ b/docs/admin/authentication.md
@@ -12,4 +12,4 @@ In order to use Telegram as an AP you need to be hosting Owltide under a domain
 
 You will also need a bot which can be created by messaging [@BotFather](https://t.me/BotFather), with the domain of the bot set using the `/setdomain` command to the domain Owltide is hosted under.
 
-Once you have the pre-requisites you need to configure `NUXT_TELEGRAM_BOT_TOKEN_FILE` to a path to a file containing the token of the bot with no spaces or new-lines.  `NUXT_PUBLIC_TELEGRAM_BOT_USERNAME` to the username of the bot.  And finally `NUXT_PUBLIC_AUTH_TELEGRAM_ENABLED` to `true` to enable authentication via Telegram.
+Once you have the pre-requisites you need to configure `NUXT_TELEGRAM_BOT_TOKEN_FILE` to a path to a file containing the token of the bot with no spaces or new-lines.  `NUXT_PUBLIC_TELEGRAM_BOT_USERNAME` to the username of the bot.  And finally `NUXT_AUTH_TELEGRAM_ENABLED` to `true` to enable authentication via Telegram.
diff --git a/docs/admin/config.md b/docs/admin/config.md
index e891aca..cf22886 100644
--- a/docs/admin/config.md
+++ b/docs/admin/config.md
@@ -20,7 +20,7 @@ Time in seconds before a session is deleted from the client and server, resultin
 
 This should be several times greater that `NUXT_SESSION_ROTATES_TIMEOUT`.
 
-### NUXT_PUBLIC_AUTH_DEMO_ENABLED
+### NUXT_AUTH_DEMO_ENABLED
 
 Boolean indicating if the demo authentication provider should be enabled. This allows logging in using only a name with no additional checks or security and should _never_ be enabled on a production system. The purpose of this is to make it easier to demo the system.
 
@@ -30,15 +30,15 @@ Defaults to `false`.
 
 Path to a file containing the token for the Telegram bot used for authenticating users via Telegram.
 
-Does nothing if `NUXT_PUBLIC_AUTH_TELEGRAM_ENABLED` is not enabled.
+Does nothing if `NUXT_AUTH_TELEGRAM_ENABLED` is not enabled.
 
 ### NUXT_PUBLIC_TELEGRAM_BOT_USERNAME
 
 Username of the Telegram bot used for authenticating users via Telegram.
 
-Does nothing if `NUXT_PUBLIC_AUTH_TELEGRAM_ENABLED` is not enabled.
+Does nothing if `NUXT_AUTH_TELEGRAM_ENABLED` is not enabled.
 
-### NUXT_PUBLIC_AUTH_TELEGRAM_ENABLED
+### NUXT_AUTH_TELEGRAM_ENABLED
 
 Boolean indicating if authentication via Telegram is enabled or not. Requires `NUXT_PUBLIC_TELEGRAM_BOT_USERNAME` and `NUXT_TELEGRAM_BOT_TOKEN_FILE` to be set in order to work.
 
diff --git a/tools/tag-release.sh b/tools/tag-release.sh
deleted file mode 100755
index c5527fa..0000000
--- a/tools/tag-release.sh
+++ /dev/null
@@ -1,11 +0,0 @@
-#!/bin/bash
-
-# Finds the next available r<year>.<month>.<increment> identifier
-YEAR_MONTH=$(date -u +%Y.%-m)
-YEAR=${YEAR_MONTH:0:4}
-MONTH=${YEAR_MONTH:5}
-LAST_INCREMENT=$(git tag --list | grep '^r[1-9][0-9]*\.\([1-9]\|1[0-2]\)\.\(0\|[1-9][0-9]*\)$' | cut -d . -f 3 | sort -nr | head -n 1)
-RELEASE=r${YEAR_MONTH}.$(( ${LAST_INCREMENT:--1} + 1 ))
-
-git tag $RELEASE
-echo Tagged $RELEASE