-
Notifications
You must be signed in to change notification settings - Fork 66
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
Release action #34
Release action #34
Conversation
* tweak release publishing settings.
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.
Looks good, just a few questions
- linux | ||
- windows | ||
- darwin | ||
- id: sbom |
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.
Is our intent to provide signed releases of every standalone plugin?
tags: | ||
- 'v*' | ||
|
||
jobs: |
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.
A sample image of how the release looks might be helpful?
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.
uses: goreleaser/goreleaser-action@v2 | ||
with: | ||
version: latest | ||
args: release --rm-dist |
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.
maybe we can add dist/* to our .gitignore. I see your change for ignoring dist, do we still need this --rm-dist?
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.
It might not be strictly necessary but I think it will help with insuring clean builds especially if we start making this more complicated.
dir: plugins/verifier/sbom | ||
binary: sbom | ||
env: | ||
- CGO_ENABLED=0 |
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.
nit: is this needed?
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.
From my little bit of research this looks like it will make our packaged binary more portable. The default is 1, it seems like that means our packaged binaries can look for various C-runtime binaries on the machine it's running on and would fail if they are missing. With 0 it sounds like everything will be included in the packaged binary.
- darwin | ||
- id: sbom | ||
dir: plugins/verifier/sbom | ||
binary: sbom |
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.
Is there a reason as to why we are building only one plugin? We need to think about how we release our plugins
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.
I was just following what Makefile builds. I can include more.
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.
I would say let's track this as another issue if we want to add more assets to the build.
snapshot: | ||
name_template: "{{ incpatch .Version }}-next" | ||
changelog: | ||
sort: asc |
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.
is it by commit time? will it preferred to be desc?
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.
It will be by commit message in alphabetical order.
sort: asc | ||
filters: | ||
exclude: | ||
- '^docs:' |
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.
Nice
Fixes #16 |
If there are more comments - let's open them as issues. |
* initial goreleaser and action configuration * * update release documentation * tweak release publishing settings. * some documentation edits * tweak some Go settings and add names
Adds a goreleaser action that will create a draft release when pushing a tag that begins with v*. The release can be reviewed and release notes enhanced before being published.
Also update release documentation to reflect this action.