Open
Conversation
* Update dockerfile to build from source * Add workflows for test on push, publish docker on release, and publish executbles on release * typo * updated name * fixed finger problem
* Update dockerfile to build from source * Add workflows for test on push, publish docker on release, and publish executbles on release * typo * updated name * fixed finger problem * Fix Docker Push
* Update dockerfile to build from source * Add workflows for test on push, publish docker on release, and publish executbles on release * typo * updated name * fixed finger problem * Fix Docker Push * Remove 386
Contributor
Author
|
There is no workflow to run release.py Probably should be run on release: {created] |
Owner
|
GoReleaser automatically creates the changelog for the GitHub release based on the commit messages, doesn't it? That way, we wouldn't need release.py anymore. |
Contributor
Author
|
I think you are correct about GoReleaser but I have added a new workflow to run release.py on a release creation as well. If GoReleaser works as we think it does, after the next release can delete the release_check workflow. |
Bumps [github.com/spf13/viper](https://github.com/spf13/viper) from 1.9.0 to 1.15.0. - [Release notes](https://github.com/spf13/viper/releases) - [Commits](spf13/viper@v1.9.0...v1.15.0) --- updated-dependencies: - dependency-name: github.com/spf13/viper dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [github.com/fatih/color](https://github.com/fatih/color) from 1.13.0 to 1.17.0. - [Release notes](https://github.com/fatih/color/releases) - [Commits](fatih/color@v1.13.0...v1.17.0) --- updated-dependencies: - dependency-name: github.com/fatih/color dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
Bumps [github.com/spf13/cobra](https://github.com/spf13/cobra) from 1.2.1 to 1.8.0. - [Release notes](https://github.com/spf13/cobra/releases) - [Commits](spf13/cobra@v1.2.1...v1.8.0) --- updated-dependencies: - dependency-name: github.com/spf13/cobra dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
…m/fatih/color-1.17.0 Bump github.com/fatih/color from 1.13.0 to 1.17.0
…m/spf13/cobra-1.8.0 Bump github.com/spf13/cobra from 1.2.1 to 1.8.0
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Created 3 workflows to address #196
requires DOCKERHUB_USERNAME and DOCKERHUB_TOKEN repository secrets
1 & 2 run after a published release or can be run manually (workflow_dispatch)
3 will run on every push
Also updated Dockerfile to create a pure static executable negating the need to simlink libraries