AL-Go version
9.1
Describe the issue
Hi,
when running action publish to environment and selecting current as version.
When no release artifact is found, it failbacks to the latest CI/CD artifact.
This failback is not available when running action publish to appsource., there we have to choose latest version.
Can you also provide this failback in the publish to appsource workflow?
Expected behavior
When running action publish to appsource and leaving the version to current, it should behave like the action publish to environment and select the latest CI/CD artifact
Steps to reproduce
see above
Additional context (logs, screenshots, etc.)
No response
AL-Go version
9.1
Describe the issue
Hi,
when running action publish to environment and selecting current as version.
When no release artifact is found, it failbacks to the latest CI/CD artifact.
This failback is not available when running action publish to appsource., there we have to choose latest version.
Can you also provide this failback in the publish to appsource workflow?
Expected behavior
When running action publish to appsource and leaving the version to current, it should behave like the action publish to environment and select the latest CI/CD artifact
Steps to reproduce
see above
Additional context (logs, screenshots, etc.)
No response