-
Notifications
You must be signed in to change notification settings - Fork 86
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
Issue-153: Adding a github workflow for handling releases. #239
Conversation
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.
Couple of inline comments... I do think the build
workflow could be updated with RISC-V support if we want to keep that over Go Releaser. I think that was just missed in #205.
@cipherboy I think I got all of your in-lines. |
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 don't see a reason to hold this up any further... I suspect the new layout of packages will break existing users expecting drop-in replacement. And I'd like to see the existing (now broken) build scripts removed in the future. But these are nitpicks to deal with later.
Signed-off-by: Nathan Phelps <naphelps@us.ibm.com>
Signed-off-by: Nathan Phelps <naphelps@us.ibm.com>
… a destination directoy path for openbao.service. Signed-off-by: Nathan Phelps <naphelps@us.ibm.com>
Signed-off-by: Nathan Phelps <naphelps@us.ibm.com>
…ries in the same directory structure as the existing Dockerfile. Signed-off-by: Nathan Phelps <naphelps@us.ibm.com>
…or bsd, solaris, wasm, and arch linux. Signed-off-by: Nathan Phelps <naphelps@us.ibm.com>
Signed-off-by: Nathan Phelps <naphelps@us.ibm.com>
References: #153
Changes: