Check config file changes on abra release #684

New Issue

iexos · 2025-10-01T10:54:10Z

iexos commented

2025-10-01 10:54:10 +00:00

One common error that I encountered before is that app upgrade failed because the maintainer forgot to push a config file version in abra.sh. My proposal to mitigate this issue is by doing checks when running abra recipe release:

collect all config file paths by extracting them from compose*.yml, i.e. configs: *: file: <path>
check if there were changes to any of these files after last release
if there were, check if config version in abra.sh did change
if it didn't, notify and abort

This might not be needed if testing upgrades are done by CI, though as this is a common mistake I think it would be helpful to catch it as early as possible. Also, it can easily catch all instances even if not all configurations would be tested.

One common error that I encountered before is that `app upgrade` failed because the maintainer forgot to push a config file version in `abra.sh`. My proposal to mitigate this issue is by doing checks when running `abra recipe release`: * collect all config file paths by extracting them from `compose*.yml`, i.e. `configs: *: file: <path>` * check if there were changes to any of these files after last release * if there were, check if config version in `abra.sh` did change * if it didn't, notify and abort This might not be needed if testing upgrades are done by CI, though as this is a common mistake I think it would be helpful to catch it as early as possible. Also, it can easily catch all instances even if not all configurations would be tested.

👍 3

iexos referenced this issue from toolshed/organising

2025-10-01 11:02:13 +00:00

Improving the recipe release process #663

decentral1se added this to the Abra v0.12 project 2025-10-01 13:21:27 +00:00

decentral1se added the

enhancement

label 2025-10-02 09:11:15 +00:00

decentral1se modified the project from Abra v0.12 to Abra "next"

2025-10-26 09:50:18 +00:00

Sign in to join this conversation.