Upgrade to 10.2.0+2026.2.1 #21

2026-03-05T16:02:31Z

notplants commented

2026-03-05 16:02:31 +00:00

Hi, I tried to work on this upgrade to the latest, but not super familiar with this recipe, if someone wants to take a look, or test it out?

From my local testing, if I updated directly to the latest version, there were migration errors. Which the authentik docs talk about here:

Upgrade sequence: Upgrades must follow the sequence of major releases; do not skip directly from an older major version to the most recent version.

So this PR actually includes two releases. An intermediate release (to 10.1.5+2025.12.4) , and then the latest. From my testing, going to the intermediate then to the latest seemed to work, but skipping the intermediate did not. I tried to add release notes to indicate this (although its a bit of a headache for operators...)

The authentik release notes also mentioned moving /media to /data/media (https://docs.goauthentik.io/releases/2025.12#storage-mount-changes), but it appeared there was a symlink in the container from /media to /data/media so it seemed like I could just keep the volume at /media and it was working

A set_icon endpoint was also deleted in this release (https://docs.goauthentik.io/releases/2025.12#whats-deleted), so I tried to fix the abra.sh set_icon function that was previously making use of that endpoint.

Second pair of eyes would be appreciated!

Hi, I tried to work on this upgrade to the latest, but not super familiar with this recipe, if someone wants to take a look, or test it out? From my local testing, if I updated directly to the latest version, there were migration errors. Which the authentik [docs](https://docs.goauthentik.io/install-config/upgrade) talk about here: > Upgrade sequence: Upgrades must follow the sequence of major releases; do not skip directly from an older major version to the most recent version. So this PR actually includes two releases. An intermediate release (to 10.1.5+2025.12.4) , and then the latest. From my testing, going to the intermediate then to the latest seemed to work, but skipping the intermediate did not. I tried to add release notes to indicate this (although its a bit of a headache for operators...) The authentik release notes also mentioned moving /media to /data/media (https://docs.goauthentik.io/releases/2025.12#storage-mount-changes), but it appeared there was a symlink in the container from /media to /data/media so it seemed like I could just keep the volume at /media and it was working A set_icon endpoint was also deleted in this release (https://docs.goauthentik.io/releases/2025.12#whats-deleted), so I tried to fix the abra.sh set_icon function that was previously making use of that endpoint. Second pair of eyes would be appreciated!

notplants added 2 commits 2026-03-05 16:02:32 +00:00

chore: publish 10.1.5+2025.12.4 release f9fd1f9a5f

Intermediate step for upgrading to 2026.2.x.
Bump authentik to 2025.12.4, postgres to 15.17.

chore: publish 10.2.0+2026.2.1 release 9d621ed1de

notplants commented

2026-03-05 16:05:17 +00:00

tagging some recent commiters @moritz @carla @simon

apologies if I'm missing context that is needed here

tagging some recent commiters @moritz @carla @simon apologies if I'm missing context that is needed here

notplants added 1 commit 2026-03-05 18:14:48 +00:00

Merge branch 'main' into authentik-upgrade a7b7f1b718

moritz commented

2026-03-09 11:13:49 +00:00

Thank you very much for this update 🚀
At first glance, it looks good. The next week we will we commit completely on updates at LIT. Then we will test it out and merge it if everything works out.

Thank you very much for this update 🚀 At first glance, it looks good. The next week we will we commit completely on updates at LIT. Then we will test it out and merge it if everything works out.

👍 1

moritz commented

2026-03-16 22:00:12 +00:00

I tested the update process and it works flawlessly 🎉
I picked your commits and rearranged the versioning.

I tested the update process and it works flawlessly 🎉 I picked your commits and rearranged the versioning.

❤️ 1

moritz closed this pull request

2026-03-16 22:00:12 +00:00

notplants commented

2026-03-17 18:34:55 +00:00

@moritz oops, after deploying this to some more autonomic servers, noticed that there was a missing font (which leads to missing icons) after the upgrade to 10.2

it seems that the assets volume needs to be removed, in order for authentik to then regenerate assets on load, so that the icons appear

I was able to fix this on some deployments via:

abra app undeploy <app-name>
docker volume rm <stack_name>_assets
abra app deploy <app-name>

alternatively this could be fixed by removing the named volume for assets from the recipe (unless there are user persisted files in that assets directory?):

      - assets:/web/dist/assets

it looks to me like customize in abra.sh might be the only thing messing with custom assets there

a big headache for some custom assets, but having trouble thinking of the most elegant way to resolve this

@moritz oops, after deploying this to some more autonomic servers, noticed that there was a missing font (which leads to missing icons) after the upgrade to 10.2 it seems that the assets volume needs to be removed, in order for authentik to then regenerate assets on load, so that the icons appear I was able to fix this on some deployments via: ``` abra app undeploy <app-name> docker volume rm <stack_name>_assets abra app deploy <app-name> ``` alternatively this could be fixed by removing the named volume for assets from the recipe (unless there are user persisted files in that assets directory?): ``` - assets:/web/dist/assets ``` it looks to me like `customize` in abra.sh might be the only thing messing with custom assets there a big headache for some custom assets, but having trouble thinking of the most elegant way to resolve this

notplants commented

2026-03-17 18:47:00 +00:00

My best idea right now is to add a clear_assets function to abra.sh

clear_assets() {
  rm -rf /web/dist/assets/*
  echo "Assets cleared. Redeploy to repopulate from image, then run 'customize' if needed."
}

So after upgrade, the user can run abra app cmd <appname> app clear_assets --user root and then redeploy and the assets should be fixed. They would then need to rerun customize if they had customizations.

My best idea right now is to add a clear_assets function to abra.sh ``` clear_assets() { rm -rf /web/dist/assets/* echo "Assets cleared. Redeploy to repopulate from image, then run 'customize' if needed." } ``` So after upgrade, the user can run `abra app cmd <appname> app clear_assets --user root` and then redeploy and the assets should be fixed. They would then need to rerun customize if they had customizations.

notplants referenced this pull request

2026-03-17 19:22:37 +00:00

chore: publish 11.0.2+2026.2.1 release #23

Pull request closed

Please reopen this pull request to perform a merge.

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/authentik#21

Allow edits from maintainers