-
Notifications
You must be signed in to change notification settings - Fork 407
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
Publish gh release binaries #44
Comments
When #45 lands, I will make a tag and a companion release |
Sweet. |
I added Mac and linux64 builds -- hopefully that is enough? |
Personally, I also need this on Windows. |
Mac is perfect for me. Linux will be great for ci validation. Thanks @pmbethe09! |
I don't have a good way to make a Windows release -- let me ask the bazel team for suggestions |
looks like the links for the OSX release bins are invalid here https://github.com/bazelbuild/buildifier/releases. is this the right place to look? |
Not sure how that happened, but I have fixed this.
…On Sat, Feb 4, 2017 at 6:11 PM, doug tangren ***@***.***> wrote:
looks like the links for the OSX release bins are invalid here
https://github.com/bazelbuild/buildifier/releases. is this the right
place to look?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#44 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ALF-0kt5bXXNAIgawA1wE3CF0m1nvKbQks5rZQWTgaJpZM4LwmyL>
.
|
@pmbethe09 The OSX release worked for me, but the Linux one claims that it does not support the |
... No not sure. We need a better release process as these were ad-hoc. |
@pmbethe09 You might be able to have Circle-CI do the build and publish it for you. That's what we do for Nuclide, and the setup does not appear to be Also, FWIW, have you just been changing the binaries under the release tag rather than stamping out a new release with its own version number? It feels a little dodgy to just change the binaries in-place. |
Yes, but only because I didn't know what I was doing -- no more changes as of now :) |
No worries: I'm sure 0.4.4 will go much smoother! |
closing as automation and Windows are covered in other issues |
I'd like my team to use this tool without forcing them all to install the go runtime
The text was updated successfully, but these errors were encountered: