-
-
Notifications
You must be signed in to change notification settings - Fork 542
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
installation of v13.0.0-alpha.1 #1074
Comments
Thank you for your issue! I'm not sure if the next release will, the hope is that it will, and they will be back before |
wonderful, good to know, thank you! |
Categorizing alpha releases as pre-releases would prevent interference with automated pipelines. Tagging them appropriately ensures they don't disrupt automated workflows, maintaining pipeline integrity while allowing necessary testing during the alpha stage. |
Well, if you want stability in an automated pipeline, I would recommend pinning to a specific version and manually upgrading, as even if those builds were distributed, there could be breaking changes that break your workflows. |
I respect your suggestion to pin specific versions for stability. However, categorizing alpha releases as pre-releases is a common practice to maintain pipeline integrity during testing phases. |
Well, nobody is paying me to maintain the integrity of their pipeline, so that is out of scope for the project. |
I agree, but the suggestion seems valid to me, and it is also very easy to do. you simply go to releases and add the prerelease tag. |
First of all thanks for this amazing tool, it's great to see ongoing progress on the project! 🙏
The latest release
v13.0.0-alpha.1
doesn't come with pre-built binaries, unlike those before. However, the installation instructions inREADME.md
are unchanged and still suggest installation of a binary build downloaded from the release page.Will the next release have prebuilt binaries again? This is relevant to me because the current release breaks our automated workflow for provisioning disposable dev environments. Thank you very much!
The text was updated successfully, but these errors were encountered: