Show changelog when deploying with tag/-l #804

New Issue

2026-03-24T16:24:11Z

iexos commented

2026-03-24 16:24:11 +00:00

When an app is undeployed, I can deploy a later version than has been deployed before, maybe containing breaking changes. I think the only way to determine the previously deployed version is the env version? Based on that I would like:

show release notes between previous and new deployment
show a warning if previous version cannot be determined (e.g. chaos commit)
show a big warning, if the deployment will be a downgrade

This might be a bit brittle as the env version might not always be correct, so maybe a warning about this as well? At the very least there should be a hint to check the release notes if --latest is given.

Background: I may have broken my (not backed up) test deployment of authentik because I didn't realize release notes are not shown 😬

When an app is undeployed, I can deploy a later version than has been deployed before, maybe containing breaking changes. I think the only way to determine the previously deployed version is the env version? Based on that I would like: - show release notes between previous and new deployment - show a warning if previous version cannot be determined (e.g. chaos commit) - show a big warning, if the deployment will be a downgrade This might be a bit brittle as the env version might not always be correct, so maybe a warning about this as well? At the very least there should be a hint to check the release notes if `--latest` is given. Background: I may have broken my (not backed up) test deployment of authentik because I didn't realize release notes are not shown 😬

decentral1se added the enhancement label 2026-03-24 19:48:45 +00:00

decentral1se commented

2026-03-24 19:51:44 +00:00

Oh damnit, that is indeed a pretty big oversight. Good that you raised this issue! Hope your deployment is not broken 🙏 I guess in the deploy code path, we can indeed compare the .env version to the deployVersion and then make some decisions on what to do. There might also be a way to include this in the deployment overview also.

Oh damnit, that is indeed a pretty big oversight. Good that you raised this issue! Hope your deployment is not broken 🙏 I guess in the `deploy` code path, we can indeed compare the `.env` version to the `deployVersion` and then make some decisions on what to do. There might also be a way to include this in the deployment overview also.

👍 1

decentral1se added this to the Abra "next" project 2026-03-24 19:51:48 +00:00

iexos referenced this issue

2026-03-25 16:42:32 +00:00

`abra app upgrade` randomly misses release notes #807

Sign in to join this conversation.