Using -ne wasn't such a good idea since it would do a numeric compare.
Now use -n which checks if the length is non-zero. APK prints the
problematic version if - problematic - so this should now do the trick.
Signed-off-by: Paul Spooren <mail@aparcar.org>
This action was mostly based on the autorelease CI job and somehow there
is an error that if multiple packages are affected, the path is
concatenated instead of adding a space.
Secondly the APK return code 0 wasn't good enough for the if condition
and caused it to trigger even on valid versions.
Signed-off-by: Paul Spooren <mail@aparcar.org>
APK uses a deterministic version schema, have the CI check that changed
packages actually follow that version schema.
Signed-off-by: Paul Spooren <mail@aparcar.org>