-
Notifications
You must be signed in to change notification settings - Fork 14
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
ci: Build binaries using goreleaser #440
Conversation
@glimchb Can you approve the workflows? |
runs-on: ubuntu-latest | ||
steps: | ||
- name: Checkout | ||
uses: actions/checkout@v4 |
Check warning
Code scanning / Scorecard
Pinned-Dependencies Medium
Remediation tip: update your workflow using https://app.stepsecurity.io
Click Remediation section below for further remediation help
fetch-depth: 0 | ||
|
||
- name: Set up Go | ||
uses: actions/setup-go@v5 |
Check warning
Code scanning / Scorecard
Pinned-Dependencies Medium
Remediation tip: update your workflow using https://app.stepsecurity.io
Click Remediation section below for further remediation help
cache-dependency-path: sztp-agent/go.sum | ||
|
||
- name: Run GoReleaser | ||
uses: goreleaser/goreleaser-action@v6 |
Check warning
Code scanning / Scorecard
Pinned-Dependencies Medium
Remediation tip: update your workflow using https://app.stepsecurity.io
Click Remediation section below for further remediation help
- '*' | ||
|
||
permissions: | ||
contents: write |
Check failure
Code scanning / Scorecard
Token-Permissions High
Remediation tip: Visit https://app.stepsecurity.io/secureworkflow.
Tick the 'Restrict permissions for GITHUB_TOKEN'
Untick other options
NOTE: If you want to resolve multiple issues at once, you can visit https://app.stepsecurity.io/securerepo instead.
Click Remediation section below for further remediation help
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.
- small fix in commit message lower
b
inBuild
- consider just adding to existing
release
yaml workflow file
Signed-off-by: Suraj Shirvankar <[email protected]>
cc2bb89
to
e71a698
Compare
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.
great work
Proposed changes
This PR introduces the option to build 64bit binaries for x86_64 and arm64.The releases are generated when new tags are created and pushed to the repo.
I was able to simulate it on my fork https://github.com/h0lyalg0rithm/sztp/actions/runs/10165872886
I have set the go version to 1.19 instead of 1.20 or 1.21 because of the go.mod version
Refers to this issue #432
Types of changes
What types of changes does your code introduce to the repo? Put an
x
in the boxes that applyChecklist
Put an
x
in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.