Which area this feature is related to?

/kind bug

Which area this bug is related to?

/area ci
/area alizer

Bug Summary

Describe the bug:

The scheduled nightly run which checks alizer devfile command against product & community registries is failing after the merge of devfile/registry#202. This PR has introduced a change in the tags of wildfly stack and alizer is not able to match the wildfly-bootable-jar for the starter project that the wildfly-bootable-jar stack is using.

To Reproduce:

A failure of the ci can be found here: https://github.com/devfile/alizer/actions/runs/6044934174

Expected behavior

The task should be able to match the wildfly-bootable-jar starter project with the same wildfly-bootable-jar and the task should pass.

Any logs, error output, screenshots etc? Provide the devfile that sees this bug, if applicable

Logs can be found here https://github.com/devfile/alizer/actions/runs/6044934174/job/16404241166

Suggestion on how to fix the bug

As the https://github.com/devfile/registry/pull/202/files updates the tags of the wildfly stack we might need to change the project used to check the wildfly-bootable-jar.