-
-
Notifications
You must be signed in to change notification settings - Fork 7.5k
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
Script Hugo release process #3358
Comments
@moorereason @spf13 @digitalcraftsman Have a look at https://github.com/bep/hugo/releases/tag/v0.20.110 And esp. the file names. There are some subtle differences to get it consistent, but the main ones are like before to keep old Wercker deploys working etc.
(also: I seem to have "lost" the deb builds in the example above, I will fix that). |
This is complete: |
I hadn't paid much attention to our old release filenames. They're a mess! Agree on the zip vs tar.gz change. If we keep the "32bit" replacement, I prefer "32bit" to "32-bit." Same for "64-bit." The extra hyphen just adds more noise to a busy filename. Personal preference, but I prefer all lowercase filenames. Overall, looks much cleaner. 👍 |
I'm not changing the Linux filename at all (it would break too many scripts, even some of mine). |
What do you mean? Our existing releases use "32bit" not "32-bit". |
Which is the reason I ask other people to look at it ... I stared at those filenames side-by side, and they looked the same to me ... Thanks, I will fix the bit. |
This commit adds a work flow aroung GoReleaser to get the Hugo release process automated and more uniform: * It can be run fully automated or in two steps to allow for manual edits of the relase notes. * It supports both patch and full releases. * It fetches author, issue, repo info. etc. for the release notes from GitHub. * The file names produced are mainly the same as before, but we no use tar.gz as archive for all Unix versions. * There isn't a fully automated CI setup in place yet, but the release tag is marked in the commit message with "[ci deploy]" Fixes gohugoio#3358
This commit adds a work flow aroung GoReleaser to get the Hugo release process automated and more uniform: * It can be run fully automated or in two steps to allow for manual edits of the relase notes. * It supports both patch and full releases. * It fetches author, issue, repo info. etc. for the release notes from GitHub. * The file names produced are mainly the same as before, but we no use tar.gz as archive for all Unix versions. * There isn't a fully automated CI setup in place yet, but the release tag is marked in the commit message with "[ci deploy]" Fixes #3358
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Based on https://github.com/goreleaser/goreleaser
The text was updated successfully, but these errors were encountered: