[Bug]: Publish to appsource - current version failback
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 506
- Forks
- 203
- Avg merge
- 4d 22h
- Merged PRs (30d)
- 6
Description
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
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare the publish to appsource workflow with the publish to environment workflow, focusing on how each handles the current version when no release artifact is found. Trace the version and artifact-selection entry points, then verify that leaving the version as current selects the latest CI/CD artifact in the appsource workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 70/100