-
Notifications
You must be signed in to change notification settings - Fork 6
ci: add homebrew release #143
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
Conversation
|
I haven't created |
amoeba
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. Looks about right to me. Left two notes.
.goreleaser.yaml
Outdated
| - dbc@{{ .Version }} | ||
| - dbc@{{ .Major }} | ||
| - dbc@{{ .Major }}.{{ .Minor }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| - dbc@{{ .Version }} | |
| - dbc@{{ .Major }} | |
| - dbc@{{ .Major }}.{{ .Minor }} | |
| - dbc@{{ .Version }} | |
| - dbc@{{ .Major }}.{{ .Minor }} |
I think we could totally skip this but at least I don't think we need all three aliases. What do you think about just Major.Minor for now?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
at a minimum we should do Version + Major/Minor
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Edited my suggestion.
.goreleaser.yaml
Outdated
| description: "A CLI utility for managing ADBC drivers" | ||
| repository: | ||
| owner: "columnar-tech" | ||
| name: "homebrew-dbc" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| name: "homebrew-dbc" | |
| name: "homebrew-tap" |
It's slightly more conventional to call the repo "homebrew-tap". That carries the benefit of us not having to rename the repo if we create more formulae/casks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it? Everything I was seeing was that it should be homebrew-${package} I thought? Though I guess you're right for the case where we might want to create more under the Columnar org...
@ianmcook thoughts?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I mean: https://github.com/charmbracelet/homebrew-tap. :) but also https://docs.brew.sh/How-to-Create-and-Maintain-a-Tap says it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have no idea, but if the docs say to use homebrew-tap then that seems like a good reason to.
|
Thanks for doing this! |
f011817 to
72b769c
Compare
|
I created |
closes #85