Describe the bug
As part of #333, the 4.10.0 tag was removed entirely. In my opinion this is excessive and introduces new issues, because any recently developed workflows that reference 4.10.0 are now broken.
The original concern was that the v4 tag should not include the 4.10.0 change. Addressing that doesn’t require deleting the 4.10.0 tag itself. A less disruptive fix would have been to point v4 back to the 4.9.x release and re-tag 4.10.0 to the previous 4.9.1 commit so that the tag remains available and existing workflows continue to work.
Current behavior
Error: Unable to resolve action `jfrog/setup-jfrog-cli@v4.10.0`, unable to find version `v4.10.0`
Reproduction steps
No response
Expected behavior
No response
Setup JFrog CLI version
4.10.0
JFrog CLI version
N/A
Workflow operating system type and version
Linux
JFrog Artifactory version (if relevant)
No response
JFrog Xray version (if relevant)
No response
Describe the bug
As part of #333, the 4.10.0 tag was removed entirely. In my opinion this is excessive and introduces new issues, because any recently developed workflows that reference 4.10.0 are now broken.
The original concern was that the v4 tag should not include the 4.10.0 change. Addressing that doesn’t require deleting the 4.10.0 tag itself. A less disruptive fix would have been to point v4 back to the 4.9.x release and re-tag 4.10.0 to the previous 4.9.1 commit so that the tag remains available and existing workflows continue to work.
Current behavior
Reproduction steps
No response
Expected behavior
No response
Setup JFrog CLI version
4.10.0
JFrog CLI version
N/A
Workflow operating system type and version
Linux
JFrog Artifactory version (if relevant)
No response
JFrog Xray version (if relevant)
No response