Closed prfarlow1 closed 3 years ago
Thanks for the detailed issue report! We are in the process of rebuilding the release infrastructure on top of GitHub Actions. As part of that, a tag for v20.8.0 was created without a corresponding release. I deleted the tag and will work with the team to resolve the issue.
I agree the bitrise step should only use the latest release, as you point out.
Hello there, I'm a bot. On behalf of the community I thank you for opening this issue.
To help our human contributors focus on the most relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 90 days, so I marked it as stale.
The community would appreciate if you could check if the issue still persists. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me".
If no comment left within 21 days, this issue will be closed.
I'll close this issue as it doesn't seem to be relevant anymore. We believe an old issue probably has a bunch of context that's no longer relevant, therefore, if the problem still persists, please open a new issue.
Right now in Flank, the latest version is 20.7.0, and there's a pre-release of 20.8.0.
In the step documentation for the version parameter, it says this: "Flank binary version. You can use any tag name that is available on https://github.com/Flank/flank/releases or latest which will download the latest non-pre-elease version." (unrelated, but there's also a typo)
Currently, the step is failing for me with a 404 because I have entered
latest
but it's still trying to pull 20.8.0