If the scheduled maintenance process is triggered by a release being done, add a safeguard to verify the release number is in the list of discovered supported releases.
As part of the 6.11 release we saw that the API did not return 6.11 also it triggered the CI run.
We can fail fast by comparing the env var carrying the release number string with the JSON array's content.
If the scheduled maintenance process is triggered by a release being done, add a safeguard to verify the release number is in the list of discovered supported releases.
As part of the 6.11 release we saw that the API did not return 6.11 also it triggered the CI run.
We can fail fast by comparing the env var carrying the release number string with the JSON array's content.