You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I am not entirely sure if this is a bug or intended. Every time, there is an update, I receive an email notification about a new available update. Now, if I immediately use the recommended way of upgrading a Docker compose installation (as described in the docs), the compose-file in question https://goauthentik.io/docker-compose.yml is still pinned on the old version.
To Reproduce
Steps to reproduce the behavior:
Wait for a new update.
Receive the email notification about the new update.
The downloaded file does not pin the updated version.
Expected behavior
After I receive the email notification, the way of upgrading described in the docs should work and therefore the compose-file should already pin the new version.
Version and Deployment (please complete the following information):
authentik version: 2024.10.1
Deployment: docker-compose
Additional context
This time, I received my email notification for 2024.10.2 around 2024-11-14T18:40Z but at the time of posting this issue 2024-11-14T19:30Z. the website still pins 2024.10.1.
The text was updated successfully, but these errors were encountered:
If you wish to update right now, you can manually change the image: line to ghcr.io/goauthentik/server:2024.10.2. Pinned to SHA sha256:f0b7af35a174fae307bc61acefc9afaa85fb074e56d7aa0d292833772a3c6051 ATM
Thanks for the reply! I figured you can manually change the compose file but I was just wondering since this has happened for the past few releases too.
Describe the bug
I am not entirely sure if this is a bug or intended. Every time, there is an update, I receive an email notification about a new available update. Now, if I immediately use the recommended way of upgrading a Docker compose installation (as described in the docs), the compose-file in question https://goauthentik.io/docker-compose.yml is still pinned on the old version.
To Reproduce
Steps to reproduce the behavior:
wget -O docker-compose.yml https://goauthentik.io/docker-compose.yml
Expected behavior
After I receive the email notification, the way of upgrading described in the docs should work and therefore the compose-file should already pin the new version.
Version and Deployment (please complete the following information):
Additional context
This time, I received my email notification for 2024.10.2 around 2024-11-14T18:40Z but at the time of posting this issue 2024-11-14T19:30Z. the website still pins 2024.10.1.
The text was updated successfully, but these errors were encountered: