App Deployment with a version lower than the one published in the environment

[CyrineCH88]

Hello,
I am facing a behaviour from the CI/CD workflow. When I try to deploy an application which version is lower than the one already published, the workflow skips the deployment (and that's ok) but the issue is that the step status is marked as successful.
Is there any way (setting) to change this behaviour to force a warning or an error when this kind of scenario happens?

[aholstrup1]

Can you share the logs for the deploy step? I see we do have some logic for outputting warnings for these cases but maybe you're not hitting one of those warnings.

[CyrineCH88]

6_Deploy to Billing_EV_FR1_Preproduction.txt

We had a message "2025-10-02T12:37:46.8483638Z Total Energies_Total Energies Billing Model_1.0.4.7.app - already installed", but the issue is that we had to go inside the log to see that the deployment was skipped, but in the workflow run the step is marked as successful (see screenshot)

[aholstrup1]

Thanks for sharing! Based on those logs I would've expected you could see a warning like this one in the workflow summary (same page your screenshot is taken from)
"App SomeApp is already installed in version 1.2.3.4, which is higher than 12.3.3, used in app.json. In order to install version 1.2.3.3, the higher version must be uninstalled first."

But looking at the logs, I can see that didn't happen. I'll investigate what happened there. Could be a bug on our end.

It wouldn't fail the whole, deploy job nor mark it as skipped.

[aholstrup1]

I think we introduced this warning as part of AL-Go version 7.3 and you're using version 7.2. In the latest release you will see a warning like this one:

[CyrineCH88]

Thanks for this quick feedback, I will update my repo to the last version then :)

[CyrineCH88]

Hi,
After the repository update, I had indeed a warning in the CI/CD but only in the annotations. The deployment status was still in green as nothing wrong happened with the deployment. Is it possible to change this behaviour to have a clear visual display of the warning in the deployment step so the user can notice clearly at first sight that the app was not deployed (a yellow or red status instead of green) without having to go through all the annotations

?

[aholstrup1]

I agree with you that in this case a yellow indicator would be the most appropriate, but I don't think this is something GitHub has at the moment.

I think our two options within AL-Go at the moment are to either:

• Mark the deployment as completed (green) but display a warning (like we do now)
• Mark the deployment as failed (red) and throw an error

We chose to implement it like the former :) If GitHub ever introduce a yellow (warning-type) status for GitHub Actions, I think this would be good use-case for such a feature.

[CyrineCH88]

Do you think it will be possible in the future to make the behaviour depend on a setup rather than have it work by default in one way? Like we could introduce a setup parameter to force the deployment status to an error if there is a warning raised during the deployment.

[aholstrup1]

Yeah, if I could get you to create an idea on this (https://github.com/microsoft/AL-Go/discussions/new?category=ideas) then we'll see if we can find the time to implement it in the near future :)