Make tag,key_ring,key optional for release workflow.

[k4leung4]

Signed-off-by: Kenny Leung kleung@chainguard.dev

Summary

Make tag,key_ring,key optional for release workflow.

This is make it possible to cut releases completely automatically.

The tag will now increment the patch value by one if the release tag is
not specified.
For example:

• 1.5.9 => 1.5.10

Keyring and Key value from GCP project are now hardcoded.

Will remove the input key_ring and key when it dependent workflows are
updated to no longer specify them.

Ticket Link

Fixes

towards fixing https://github.com/sigstore/public-good-instance/issues/50

Release Note

[k4leung4]

@cpanato please review.

[cpanato]

for sigstore/sigstore we don't have a cloudbuild, we just tag the repository and create a GitHub release.
i think I did not pay attention much here #325 :(

maybe for sigstore/sigtore we can have a workflow just to create the GH and push the changelog

[k4leung4]

for sigstore/sigstore we don't have a cloudbuild, we just tag the repository and create a GitHub release. i think I did not pay attention much here #325 :(

maybe for sigstore/sigtore we can have a workflow just to create the GH and push the changelog

Agree. sigstore/sigstore will need it's own release workflow.
This workflow was meant for reuse in cosign, rekor and fulcio.

[cpanato]

for sigstore/sigstore we don't have a cloudbuild, we just tag the repository and create a GitHub release. i think I did not pay attention much here #325 :(
maybe for sigstore/sigtore we can have a workflow just to create the GH and push the changelog

Agree. sigstore/sigstore will need it's own release workflow. This workflow was meant for reuse in cosign, rekor and fulcio.

ahh true, sorry Monday.... 🤦