search

XAMPPRocky / tokei

Count your code, quickly.
Other
10.99k stars 532 forks source link

installation of v13.0.0-alpha.1 #1074

Open JKatzwinkel opened 6 months ago

JKatzwinkel commented 6 months ago

First of all thanks for this amazing tool, it's great to see ongoing progress on the project! :pray:

The latest release v13.0.0-alpha.1 doesn't come with pre-built binaries, unlike those before. However, the installation instructions in README.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!

XAMPPRocky commented 6 months ago

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!

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 v13.0.0 is released, I'm moving the project to newer release infrastructure that makes it easier to have more frequent releases, and unfortunately that didn't work with the old stuff, so the hope is that it's fixed and the next release will have it, and that I'll try to fix it for the release after that if not.

JKatzwinkel commented 6 months ago

wonderful, good to know, thank you!

psy183 commented 6 months ago

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.

XAMPPRocky commented 6 months ago

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.

psy183 commented 6 months ago

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.

XAMPPRocky commented 6 months ago

Well, nobody is paying me to maintain the integrity of their pipeline, so that is out of scope for the project.

xabru commented 6 months ago

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.