-
Notifications
You must be signed in to change notification settings - Fork 1
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
Update case of binary in goreleaser #1
Conversation
@pcjun97 very cool plugin! What do you think of this change? |
Hey @accorvin, thanks for noticing this issue and opening a PR for it! I prefer if the
Something like: project_name: HashAnnotator
builds:
- binary: '{{ .ProjectName }}'
archives:
- id: latest
name_template: '{{ tolower .ProjectName }}_latest_{{ .Os }}_{{ .Arch }}' |
f5026bd
to
cdbab10
Compare
Thanks @pcjun97! I had the same thought. I've never used goreleaser before so I wasn't sure if changing the project name would cause any other unexpected issues so wanted to get your input first. Updated. |
We hit an issue when attempting to use this plugin as installed from the GitHub release archive. It appears that Kustomize expects the case of the plugin's binary to match the `Kind` in the hashannotator object. This change updates the goreleaser.yaml file to create a binary with the correct tense.
LGTM! |
cdbab10
to
ec9634e
Compare
@pcjun97 done. |
Thanks @pcjun97! Do you know if a new release will automatically be produced? |
@accorvin Sorry for the delay. You can find the latest release here: https://github.com/pcjun97/kustomize-hash-annotator/releases/tag/1.0.1 |
We hit an issue when attempting to use this plugin as installed from the
GitHub release archive. It appears that Kustomize expects the case of
the plugin's binary to match the
Kind
in the hashannotator object.This change updates the goreleaser.yaml file to create a binary with the
correct tense.