GoReleaser builds Go binaries as fast and easily as possible

Related tags

Build Tools go docker homebrew golang package deb rpm apk travis release-automation snapcraft
Overview

GoReleaser Logo

GoReleaser

Deliver Go binaries as fast and easily as possible.

GoReleaser builds Go binaries for several platforms, creates a GitHub release and then pushes a Homebrew formula to a tap repository. All that wrapped in your favorite CI.

This project adheres to the Contributor Covenant code of conduct. By participating, you are expected to uphold this code. We appreciate your contribution. Please refer to our contributing guidelines for further information.

For questions, support and general discussion, please use GitHub Discussions;

Get GoReleaser

Documentation

Documentation is hosted live at https://goreleaser.com

Badges

Release Software License Build status Codecov branch Go Doc SayThanks.io Powered By: GoReleaser Backers on Open Collective Sponsors on Open Collective Conventional Commits

Sponsors

Does your company use goreleaser? Help keep the project bug-free and feature rich by sponsoring the project.

Backers

Love our work and community? Become a backer.

Contributors

This project exists thanks to all the people who contribute. [Contribute].

Stargazers over time

Stargazers over time

Comments
  • Complete history in changelog on every release

    Complete history in changelog on every release

    Describe the bug

    Every release I do, I get a list of every commit despite using a simple semver version. I manually edit the commits down each time.

    To Reproduce

    I release using this file.

    Expected behavior

    I expect it to pick up commits since the last released version.

    Environment (please complete the following information):

    • OS: mac
    • OS version: Darwin theganyo-macbookpro2.roam.corp.google.com 18.2.0 Darwin Kernel Version 18.2.0: Thu Dec 20 20:46:53 PST 2018; root:xnu-4903.241.1~1/RELEASE_X86_64 x86_64
    • GoReleaser Version 0.104.0, commit 7c4352147b6d9636f13d2fc633cfab05d82d929c, built at 2019-03-20T02:18:40Z
    bug 
    opened by theganyo 43
  • Support Cosign keyless signing & verification

    Support Cosign keyless signing & verification

    Is your feature request related to a problem? Please describe. It is not related to a problem. It's a feature request for signing and verifying with Keyless Mode.[^1]

    Describe the solution you'd like

    GoReleaser can use the cosign tool as a command in the sigs section. In order to enable Keyless mode in cosign, we need to pass an environment variable called COSIGN_EXPERIMENTAL=1. So, we've opened another issue to enable passing environment variables to the sigs section. Also, recently, the Kyverno project did the same thing. [^2]

    [ ] - https://github.com/goreleaser/goreleaser/issues/2657 - @Dentrax

    Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

    Additional context [^1]: https://github.com/sigstore/cosign/blob/main/KEYLESS.md [^2]: github.com/kyverno/kyverno/pull/2677

    cc: @dentrax @erkanzileli

    enhancement 
    opened by developer-guy 41
  • Release to GitLab

    Release to GitLab

    As @bernardoVale mentioned #on Slack it would be nice to support releasing to GitLab. There is a Go package for the API https://github.com/xanzy/go-gitlab. Since we also plan on adding Bintray support in #15 we might be able to combine some of the releasing logic.

    enhancement wontfix 
    opened by jorinvo 36
  • Refactor: context

    Refactor: context

    Refactor of the context package.

    We now have an artifact package.

    We now have an artifact type which can be filtered anywhere in the code, as well as filter compositions. With this set of features, we dont need specific fields for each type of artifact.

    The mutex also is in the artifact package, and we have an Artifacts type, which contains both the slice and the mutex, and also have the Add, List and Filter methods.

    I end up fixing some thing I found along the way and/or didn't work at all before:

    • docker ims from binary releases
    • multiple darwin amd64 builds on homebrew
    • Path now is always the full path (dist + folder + artifact) - before some pipes were using it differently and we have several filepath.Join(dist, artifact.Path) or similar around
    • the artifactory pipe was greatly simplified due to the previous changes
    • brew and artifactory pipes had some missing test cases which were added
    • the build pipe no longer needs to know anything about naming templates (it was a hidden dependency)
    • improved docs in several places

    I also have placed several TODOs and opened a few issues to cover problems I've found.

    This patch should allow us to add more types of artifacts easily, since all fields can be available.

    I also included an Extra field which is a map[string]string, so some pipes can add additional info (right now only the build pipe is using it).

    closes #455 closes #449

    opened by caarlos0 34
  • [Bug]: Goreleaser silently for invalid credentials on S3 uploads

    [Bug]: Goreleaser silently for invalid credentials on S3 uploads

    What happened?

    When doing a release with S3 my credentials were not set properly. goreleaser ran to completion and did not raise any errors that the S3 uploads fail.

    How can we reproduce this?

    1. Create a .goreleaser.yml that uploads to an S3 bucket.
    2. Remove credentials that give write access to that bucket
    3. Run goreleaser

    This should run to completion without alerting that the S3 uploads failed.

    goreleaser version

    goreleaser version 0.183.0
commit: be6199f08167cc85b0b16cefc02d8106237853b1
built by: homebrew

https://goreleaser.com

    GoReleaser Check

    • [X] goreleaser check shows no errors

    Search

    • [X] I did search for other open and closed issues before opening this.

    Code of Conduct

    • [X] I agree to follow this project's Code of Conduct

    Additional context

    No response

    bug 
    opened by rnikoopour 32
  • packagecloud.io http 500 error on RPMs built with v0.120.x

    packagecloud.io http 500 error on RPMs built with v0.120.x

    Describe the bug

    Since the new RPM code in nfpm and goreleaser 0.120.x was introduced it is no longer possible to push RPMs to packagecloud.io.

    Packagecloud support response:

    This package is missing a lot of required RPM headers that must appear in the YUM metadata so that YUM can find this package and install it from a repository.

    I would suggest that the maintainer of this package spend some time reviewing the RPM documentation and/or requesting the tool they use for generating the RPM automatically all required RPM headers. There's lots of possible malformed RPM packages that will make our system 500; we catch a lot of the cases, but we do miss a few and will still 500 in some rare, isolated cases (like this package, which is significantly malformed).

    To Reproduce

    Steps to reproduce the behavior:

    It should be possible to reproduce this bug locally from the https://github.com/pantheon-systems/pauditd project:

    git clone [email protected]:pantheon-systems/pauditd.git
cd pauditd

curl -sL https://git.io/goreleaser | bash -s -- --snapshot --rm-dist

    push to an existing packagecloud.io repo:

    $ package_cloud push xxx/xxx/el/8 dist/*rpm

Looking for repository at xxx/xxx... success!
Pushing dist/pauditd-v1.1.11-next-1572710235-x86_64.rpm... Traceback (most recent call last):
        23: from /usr/local/bin/package_cloud:22:in `<main>'
        22: from /usr/local/bin/package_cloud:22:in `load'
        21: from /usr/local/lib/ruby/gems/2.6.0/gems/package_cloud-0.3.05/bin/package_cloud:4:in `<top (required)>'
        20: from /usr/local/lib/ruby/gems/2.6.0/gems/thor-0.20.3/lib/thor/base.rb:466:in `start'
        19: from /usr/local/lib/ruby/gems/2.6.0/gems/thor-0.20.3/lib/thor.rb:387:in `dispatch'
        18: from /usr/local/lib/ruby/gems/2.6.0/gems/thor-0.20.3/lib/thor/invocation.rb:126:in `invoke_command'
        17: from /usr/local/lib/ruby/gems/2.6.0/gems/thor-0.20.3/lib/thor/command.rb:27:in `run'
        16: from /usr/local/lib/ruby/gems/2.6.0/gems/package_cloud-0.3.05/lib/package_cloud/cli/entry.rb:108:in `push'
        15: from /usr/local/Cellar/ruby/2.6.5/lib/ruby/2.6.0/benchmark.rb:293:in `measure'
        14: from /usr/local/lib/ruby/gems/2.6.0/gems/package_cloud-0.3.05/lib/package_cloud/cli/entry.rb:168:in `block in push'
        13: from /usr/local/lib/ruby/gems/2.6.0/gems/package_cloud-0.3.05/lib/package_cloud/cli/entry.rb:168:in `each'
        12: from /usr/local/lib/ruby/gems/2.6.0/gems/package_cloud-0.3.05/lib/package_cloud/cli/entry.rb:178:in `block (2 levels) in push'
        11: from /usr/local/Cellar/ruby/2.6.5/lib/ruby/2.6.0/benchmark.rb:293:in `measure'
        10: from /usr/local/lib/ruby/gems/2.6.0/gems/package_cloud-0.3.05/lib/package_cloud/cli/entry.rb:182:in `block (3 levels) in push'
         9: from /usr/local/lib/ruby/gems/2.6.0/gems/package_cloud-0.3.05/lib/package_cloud/cli/entry.rb:242:in `create_package'
         8: from /usr/local/lib/ruby/gems/2.6.0/gems/package_cloud-0.3.05/lib/package_cloud/repository.rb:52:in `create_package'
         7: from /usr/local/lib/ruby/gems/2.6.0/gems/rest-client-2.0.2/lib/restclient/request.rb:52:in `execute'
         6: from /usr/local/lib/ruby/gems/2.6.0/gems/rest-client-2.0.2/lib/restclient/request.rb:145:in `execute'
         5: from /usr/local/lib/ruby/gems/2.6.0/gems/rest-client-2.0.2/lib/restclient/request.rb:715:in `transmit'
         4: from /usr/local/Cellar/ruby/2.6.5/lib/ruby/2.6.0/net/http.rb:920:in `start'
         3: from /usr/local/lib/ruby/gems/2.6.0/gems/rest-client-2.0.2/lib/restclient/request.rb:725:in `block in transmit'
         2: from /usr/local/lib/ruby/gems/2.6.0/gems/rest-client-2.0.2/lib/restclient/request.rb:809:in `process_result'
         1: from /usr/local/lib/ruby/gems/2.6.0/gems/rest-client-2.0.2/lib/restclient/abstract_response.rb:103:in `return!'
/usr/local/lib/ruby/gems/2.6.0/gems/rest-client-2.0.2/lib/restclient/abstract_response.rb:223:in `exception_with_response': 500 Internal Server Error (RestClient::InternalServerError)

    Additional context

    Workaround is to use goreleaser v0.119.3, the last release before the nfpm rpm refactor.

    Apologies I cannot provide more details at this time. If I am able to determine anything helpful I'll update this thread.

    bug 
    opened by joemiller 28
  • Support multi-platform docker images

    Support multi-platform docker images

    I would like go-releaser to support releasing multi-platform docker images using something like https://github.com/estesp/manifest-tool

    This way, if the project is being built for multiple platforms, we will only use a single docker repository.

    enhancement 
    opened by pcarranza 28
  • failed to upload artifact, will retry error=POST ipsw_3.1.200_aarch64.apk: 404 Not Found

    failed to upload artifact, will retry error=POST ipsw_3.1.200_aarch64.apk: 404 Not Found

    What happened?

          • uploading to release                         file=/Users/blacktop/Developer/Github/blacktop/ipsw/dist/ipsw_3.1.200_macOS_arm64.tar.gz.sbom name=ipsw_3.1.200_macOS_arm64.tar.gz.sbom
      • failed to upload artifact, will retry        artifact=ipsw_3.1.200_aarch64.apk error=POST https://uploads.github.com/repos/blacktop/ipsw/releases/84405069/assets?name=ipsw_3.1.200_aarch64.apk: 404 Not Found [] try=1
      • uploading to release                         file=dist/ipsw_3.1.200_aarch64.apk name=ipsw_3.1.200_aarch64.apk
      • uploading to release                         file=/Users/blacktop/Developer/Github/blacktop/ipsw/dist/ipsw_3.1.200_ios_arm64.tar.gz.sbom name=ipsw_3.1.200_ios_arm64.tar.gz.sbom
      • uploading to release                         file=/Users/blacktop/Developer/Github/blacktop/ipsw/dist/ipsw_3.1.200_macOS_x86_64.tar.gz.sbom name=ipsw_3.1.200_macOS_x86_64.tar.gz.sbom
      • uploading to release                         file=/Users/blacktop/Developer/Github/blacktop/ipsw/dist/ipsw_3.1.200_linux_arm64.tar.gz.sbom name=ipsw_3.1.200_linux_arm64.tar.gz.sbom
      • uploading to release                         file=/Users/blacktop/Developer/Github/blacktop/ipsw/dist/ipsw_3.1.200_macOS_arm64_extras.tar.gz.sbom name=ipsw_3.1.200_macOS_arm64_extras.tar.gz.sbom
      • uploading to release                         file=/Users/blacktop/Developer/Github/blacktop/ipsw/dist/ipsw_3.1.200_linux_x86_64.tar.gz.sbom name=ipsw_3.1.200_linux_x86_64.tar.gz.sbom
      • uploading to release                         file=/Users/blacktop/Developer/Github/blacktop/ipsw/dist/ipsw_3.1.200_macOS_x86_64_extras.tar.gz.sbom name=ipsw_3.1.200_macOS_x86_64_extras.tar.gz.sbom
      • uploading to release                         file=/Users/blacktop/Developer/Github/blacktop/ipsw/dist/ipsw_3.1.200_macOS_universal.tar.gz.sbom name=ipsw_3.1.200_macOS_universal.tar.gz.sbom
      • uploading to release                         file=dist/checksums.txt name=checksums.txt
      • uploading to release                         file=dist/checksums.txt.sig name=checksums.txt.sig
      • failed to upload artifact, will retry        artifact=ipsw_3.1.200_aarch64.apk error=POST https://uploads.github.com/repos/blacktop/ipsw/releases/84405069/assets?name=ipsw_3.1.200_aarch64.apk: 404 Not Found [] try=1
      • uploading to release                         file=dist/ipsw_3.1.200_aarch64.apk name=ipsw_3.1.200_aarch64.apk
      • failed to upload artifact, will retry        artifact=ipsw-3.1.200.aarch64.rpm error=POST https://uploads.github.com/repos/blacktop/ipsw/releases/84405069/assets?name=ipsw-3.1.200.aarch64.rpm: 404 Not Found [] try=1

    How can we reproduce this?

    run make release in my ipsw project

    goreleaser version

    ❯ goreleaser -v
goreleaser version 1.13.1
commit: b0ffc7af05aa391b766e8e26f5ad5ec37c640d6e
built at: 2022-11-29T01:03:51Z
built by: goreleaser
goos: darwin
goarch: arm64
module version: v1.13.1, checksum: h1:9yTCn5UE3+1wNtVB3ybUAwjioLq79UyfGz8D+iPOcRk=

https://goreleaser.com

    GoReleaser Check

    • [X] goreleaser check shows no errors

    Search

    • [X] I did search for other open and closed issues before opening this.

    Code of Conduct

    • [X] I agree to follow this project's Code of Conduct

    Additional context

    I did search for other open and closed issues before opening this, but this isn't just the 422 Validation Failed [{Resource:ReleaseAsset Field:name Code:already_exists Message:}] but also WHY is nfpm making aarch64 pkgs all of the sudden?

    ipsw_3.1.200_aarch64.apk: 404 Not Found could that have something to do with it? I've tried using a pre-1.13 version of goreleaser, I've tried using a VPN and my phone as a hotspot to factor out internet and get the same issues.

    bug 
    opened by blacktop 27
  • GoReleaser Pro, open-source, and supply chain integrity

    GoReleaser Pro, open-source, and supply chain integrity

    Hi @caarlos0,

    We've been pleased to integrate goreleaser into our release process for https://github.com/fleetdm/fleet/. In particular, making it easy to build all the necessary artifacts and upload in GitHub Actions has helped with my goal to improve transparency and address software supply chain integrity issues (discussed nicely in https://security.googleblog.com/2021/06/introducing-slsa-end-to-end-framework.html).

    We are merging a couple of our repos, and purchased an enterprise license for GoReleaser Pro to support the project and utilize the monorepo functionality. I only just discovered that the goreleaser pro features are not open-source/source-available and require utilizing a separate binary. This conflicts with our goals to increase transparency and integrity in the full lifecycle of our software by adding an un-auditable dependency (GoReleaser Pro) into the build process.

    Would you consider making the code source-available? I know this is a big ask, and it's something that we have contemplated quite a bit for our business. We've settled on making everything source-available using a license that is inspired by GitLab's License.

    Otherwise we may need to find ways to work around using GoReleaser Pro features in order to move forward with transparency in our build tooling.

    Thank you for the consideration.

    enhancement wontfix 
    opened by zwass 26
  • feat: gitea release support

    feat: gitea release support

    Add support for Gitea in release pipe

    I (and probably many others) want to create releases and upload artifacts to their Gitea instances.

    Gitea: https://gitea.io/en-us/ Gitea Go SDK: https://godoc.org/code.gitea.io/sdk/gitea

    closes #1106

    enhancement 
    opened by dtluna 26
  • feat(pipe/build): Add support for flexible build hooks

    feat(pipe/build): Add support for flexible build hooks

    This is an early prototype of a solution for #1328 to solicit early feedback.

    Usage

    builds:
  -
    env:
      - CGO_ENABLED=0
    targets:
      - darwin_amd64
      - windows_386
      - windows_amd64
    after:
      all:
        hooks:
          - zip ./signable_binaries.zip {{ range .Builds }} {{ .Path }}{{ end }}
          - echo "Signing every eligible binary..."
          - cmd: ./codesign.sh
            env:
              - ZIP_FILE={{ .ProjectName }}_{{ .Version }}_{{ .Target }}.zip
      each:
        default_dir: "{{ .Path }}"
        hooks:
          - upx {{ .Name }}

    I would be happy to add some tests, perhaps some more logging and docs if we agree on the rough direction.

    opened by radeksimko 25
  • APK Keyname can be templated

    APK Keyname can be templated

    To help solve this issue

        apk:
      signature:
        key_file: "{{ .Env.ABUILD_KEY_NAME }}.rsa"
        key_name: "{{ .Env.ABUILD_KEY_NAME }}"

    Allow that the key_name in apk signature to be templated

    The name of the key might not be hardcoded, in a github workflow

    ...

    size/XS 
    opened by KalleDK 0
  • feat: add ko support

    feat: add ko support

    continuing the PR by @developer-guy

    • [x] should be a publisher, as it does publish the images it builds every time
    • [x] Default method does not work
    • [x] the fromConfig thing should probably be on the defaults, too
    • [x] wire --skip-ko
    • [x] documentation
    • [x] more tests
    • [x] use same registry as docker tests does
    • [ ] see if we can make the log output match goreleaser's
    • [ ] ??

    closes #2556 closes #3490

    enhancement size/XXL 
    opened by caarlos0 5
  • docs: d2 flow

    docs: d2 flow

    not sure how useful this is... but might help with mental models everyone has (including me), both for contributing and using goreleaser...

    I also thought about splitting it into multiple svgs, e.g.:

    • goreleaser phases ( prep , build, archive, publish etc)
    • one for each phase as well
      • especially the publish phase, which does quite a lot of things

    wdyt?

    PS: if we do use this, I'll put it inside the docs folder somewhere...

    docs size/L 
    opened by caarlos0 0
  • FYI: building Go modules via the proxy can use less code

    FYI: building Go modules via the proxy can use less code

    Is your feature request related to a problem? Please describe.

    Right now, per https://goreleaser.com/cookbooks/build-go-modules/ and gomod_proxy.go, you roughly do:

    • Create a temporary directory
    • Drop a templated main.go file
    • Drop a templated go.mod file with require main_module_path git_tag
    • Copy go.sum from the original module
    • Run go mod tidy
    • Run go build main_package_path

    You could accomplish the same with fewer steps. In particular, you don't need a main.go file, and you don't need to have a tidied module either. You could instead do:

    • Create a temporary directory
    • Run go mod init test, or use a template to get the same plain go.mod file
    • Copy go.sum from the original module
    • Run go get [email protected]_tag
    • Run go build main_package_path

    Beyond being one file and step less, this is also more powerful: you can use any VCS reference in go get [email protected], including git commit hashes, git branch names, etc.

    Also note that you don't strictly need to copy go.sum; it will still work without that step, and I reckon you don't lose any safety thanks to GOSUMDB. Though I guess you avoid a few network roundtrips if go.sum already has most of the hashes needed.

    Describe the solution you'd like

    Just suggesting a perhaps slightly better way of implementing builds via the proxy :)

    Describe alternatives you've considered

    Search

    • [X] I did search for other open and closed issues before opening this.

    Code of Conduct

    • [X] I agree to follow this project's Code of Conduct

    Additional context

    No response

    enhancement 
    opened by mvdan 1
  • Allow brew repo to have arbitrary git target

    Allow brew repo to have arbitrary git target

    Add ability for brew repos to have an arbitrary git repo as a publish target.

    Adds configuration parameters in the RepoRef config for git urls

    - name: "{{ .ProjectName }}"
    description: "My Tool Description"
    folder: Formulas
    tap:
      branch: main
      name: private-brew-tap
      git_url: "https://mygiturl.myurl.com/repo.git"
      private_key: "{{ .Env.SSH_KEY }}"

    It does not effect the function of other pipes that use RepoRef without more work to explicitly use the added fields

    To make it easier to push formulas for private git repositories

    #3525 ...

    size/XL 
    opened by graytonio 7
  • [PRO] Nightly stopped publishing releases

    [PRO] Nightly stopped publishing releases

    What happened?

    The nightly release doesn't get published even though publish_release is set to true. It creates a draft release without publishing it on GitHub.

    How can we reproduce this?

    nightly:
  name_template: "{{ .ShortCommit }}-devel"
  publish_release: true
  keep_single_release: true
  tag_name: nightly

    goreleaser version

    goreleaser v1.12.3-pro

    log 
    GoReleaser latest installed successfully
/opt/hostedtoolcache/goreleaser-action/1.12.3-pro/x64/goreleaser release --rm-dist --nightly
  • by using this software you agree with its EULA, available at https://goreleaser.com/eula
  • running goreleaser v1.12.3-pro
  • starting release...
  • loading config file                              file=.goreleaser.yml
  • loading environment variables
  • getting and validating git state
    • building...                                    commit=8341c17e16fea093856c9432439e97d72e57d3a7 latest tag=v3.3.0
    • pipe skipped                                   reason=validation is disabled
  • parsing tag
  • setting defaults
  • running before hooks
    • running hook                                   hook=rm -rf static
    • running hook                                   hook=go run .
    • took: 42s
  • nightly
    • building nightly...                            version=8341c17-devel
  • checking distribution directory
  • loading go mod information
  • build prerequisites
  • writing effective config file
    • writing                                        config=dist/config.yaml
  • adjusting internal git state
  • generating changelog
    • writing                                        changelog=dist/CHANGELOG.md
  • building binaries
    • skip is set                                    id=PROJECT
  • archives
    • creating                                       archive=dist/PROJECT-devel.tar.gz
    • took: 1s
  • calculating checksums
  • storing release metadata
    • writing                                        file=dist/artifacts.json
    • writing                                        file=dist/metadata.json
  • publishing
    • scm releases
      • creating or updating release                 repo=USER/PROJECT tag=8341c17e16fea093856c9432439e97d72e57d3a7
      • deleted previous nightly pre-release         commit=main name=e393ee05486deccd8be8d78c71a9fafe6c7fbbea tag=nightly
      • deleted previous nightly tag
      • uploading to release                         file=dist/PROJECT-devel_checksums.txt name=PROJECT-devel_checksums.txt
      • uploading to release                         file=dist/PROJECT-devel.tar.gz name=PROJECT-devel.tar.gz
      • published                                    url=https://github.com/USER/PROJECT/releases/tag/nightly
      • took: 4s
  • took: 4s
  • release succeeded after 47s
  • thanks for using goreleaser-pro!

    GoReleaser Check

    • [X] goreleaser check shows no errors

    Search

    • [X] I did search for other open and closed issues before opening this.

    Code of Conduct

    • [X] I agree to follow this project's Code of Conduct

    Additional context

    No response

    bug pro 
    opened by aymanbagabas 6
Releases(v1.14.0)
Owner
GoReleaser
Deliver Go binaries as fast and easily as possible
GoReleaser
GitHub https://goreleaser.com
Builds and restarts a Go project when it crashes or some watched file changes

gaper Used to build and restart a Go project when it crashes or some watched file changes Aimed to be used in development only. Changelog See Releases

Max Claus Nunes 64 Dec 30, 2022
🚀 gowatch is a command line tool that builds and (re)starts your go project everytime you save a Go or template file.

gowatch 中文文档 gowatch is a command line tool that builds and (re)starts your go project everytime you save a Go or template file. Installation To insta

silenceper 738 Dec 30, 2022
Please is a cross-language high-performance extensible build system for reproducible multi-language builds.

Please is a cross-language build system with an emphasis on high performance, extensibility and reproducibility. It supports a number of popular languages and can automate nearly any aspect of your build process.

Thought Machine 2.2k Dec 30, 2022
Embed static files in Go binaries (replacement for gobuffalo/packr)

Pkger github.com/markbates/pkger is a tool for embedding static files into Go binaries. It will, hopefully, be a replacement for github.com/gobuffalo/

Mark Bates 1.2k Dec 29, 2022
Golang binaries compiled on-demand for your system

Go Binaries Go Binaries is an on-demand binary server, allowing non-Go users to quickly install tools written in Go without installing go itself, and

TJ Holowaychuk 762 Dec 3, 2022
Package binaries for different operating systems in a single script, executable everywhere.

CrossBin Packages MacOS, Linux and Windows binaries, into a single script that is executable everywhere and executes the correct binary for the system

null 3 Oct 24, 2022
An extremely fast JavaScript bundler and minifier

An extremely fast JavaScript bundler and minifier

Evan Wallace 34.2k Jan 4, 2023
Monitoring changes in the source file and automatically compile and run (restart).

dogo Monitoring changes in the source file and automatically compile and run (restart). 中文 Install go get github.com/liudng/dogo Create config Here's

null 254 Dec 28, 2022
Realize is the #1 Golang Task Runner which enhance your workflow by automating the most common tasks and using the best performing Golang live reloading.

#1 Golang live reload and task runner Content - ⭐️ Top Features - ???? Get started - ?? Config sample - ?? Commands List - ?? Support and Suggestions

Oxequa 4.3k Jan 6, 2023
Various tools for usage with Golang like installer, github tool and cloud features.

Gopei2 (Go Programming Environment Installer) Gopei shell install Go compiler, LiteIDE and configure for you the entire environment, variables, paths,

George Calianu 101 Dec 23, 2022
a build tool for Go, with a focus on cross-compiling, packaging and deployment

goxc NOTE: goxc has long been in maintenance mode. Ever since Go1.5 supported simple cross-compilation, this tool lost much of its value. There are st

Am Laher 1.7k Dec 9, 2022
Build system and task runner for Go projects

Gilbert is task runner that aims to provide declarative way to define and run tasks like in other projects like Gradle, Maven and etc.

Gilbert 106 Dec 21, 2022
A small utility that aims to automate and simplify some tasks related to software release cycles.

Stork is a small utility that aims to automate and simplify some tasks related to software release cycles such as reading the current version from a f

Simone Margaritelli 41 Nov 9, 2022
Build and (re)start go web apps after saving/creating/deleting source files.

unmaintained Fresh Fresh is a command line tool that builds and (re)starts your web application everytime you save a Go or template file. If the web f

Andrea Franz 3.5k Jan 2, 2023
NFPM is Not FPM - a simple deb, rpm and apk packager written in Go

NFPM NFPM is Not FPM - a simple deb, rpm and apk packager written in Go. Why While fpm is great, for me, it is a bummer that it depends on ruby, tar a

GoReleaser 1.6k Jan 1, 2023
KintoHub is an open source build and deployment platform designed with a developer-friendly interface for Kubernetes.

What is Kintohub? KintoHub is an open source build and deployment platform designed with a developer-friendly interface for Kubernetes. Build your cod

KintoHub 30 Jun 7, 2022
Moldy CLI the best project starter and manager of the world

Moldy The best project starter of the world ?? What is Moldy ? Hey I present Moldy this beautiful tool that will solve your life in creating, managing

Moldy Community 25 Oct 17, 2022
Hooks-goreleaser - GoReleaser hooks plugin

?? hooks-goreleaser The GoReleaser integration for go-semantic-release. Usage Us

null 1 Jan 30, 2022
Bundle k6 with extensions as fast and easily as possible

xk6bundler xk6bundler is a CLI tool and GitHub Action makes bundle k6 with extensions as fast and easily as possible. Features Build for multiple targ

Iván Szkiba 10 Nov 29, 2022
A command line tool that builds and (re)starts your web application everytime you save a Go or template fileA command line tool that builds and (re)starts your web application everytime you save a Go or template file

# Fresh Fresh is a command line tool that builds and (re)starts your web application everytime you save a Go or template file. If the web framework yo

null 0 Nov 22, 2021