-
Notifications
You must be signed in to change notification settings - Fork 168
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
feat: add goreleaser and cloudbuild for releases #443
Conversation
@dlorenc @lukehinds need your thoughts here :) should we discard the cloudbuild and make a github actions with manual dispatch to trigger the release? then we can use the GH support for the OIDC and use keyless |
gently ping @dlorenc @lukehinds would like to hear the thoughts, I will apply the same behaviour for fulcio as well |
cc @asraa for comments on which keys to use here, she's working on setting up proper delegations in the sigstore root. WDYT about skipping the signing for now to get something in? |
Ok, will remove the signing part and finish it, by tomorrow we will be good to go |
I need to run se dry run before |
6972492
to
0379e77
Compare
did a rehearsal release in my fork repo using cloubuild https://github.com/cpanato/rekor/releases/tag/v99.99.99 and images
for now, we are not signing to wait for some discussion in which key we will use and this uses the same github token that cosign uses |
Using the same keys as the cosign release key would be fine since it's already inside the TUF root -- https://github.com/sigstore/root-signing/blob/main/repository/staged/targets/artifact.pub that's the public key just for double-checking ^ It's possible we re-sign targets to make the root compatible with rust TUF, in case we do this, do you want to sign with a different key that I can add? |
fe877dc
to
f842b69
Compare
this is a decision we need to make:
good things:
not so good:
|
9653621
to
b665bfa
Compare
tested the images generated by the release job in the rekor helm chart and seems to work fine
UPDATE: figured out, fixing the dockerfile UPDATE 2: fixed
|
Signed-off-by: Carlos Panato <ctadeu@gmail.com>
I would probably say sticking to one key for the sigstore org is ok for the next quarter? but ultimately up to you -- as the number of projects grow it's probably easier to have separate keys |
I think one key is fine for now. |
great, will add the signing part back, maybe later we can discuss sending the data to rekor using keyless or another approach |
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'm happy with this if you all are!
i will add the signing during the weekend and let's aim to a release early next week using this, wdyt? |
SGTM! |
oh you merged, ok i open a new pr |
Summary
Add goreleaser and cloudbuild definition to cut a rekor release, similar we do in the cosign project
Some questions to be answered:
cosign
to sing the blob/images here?Ticket Link
Related: #419
Release Note