Skip to content
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

Consider signing release artifacts #2034

Open
cary-ilm opened this issue Sep 2, 2024 · 0 comments
Open

Consider signing release artifacts #2034

cary-ilm opened this issue Sep 2, 2024 · 0 comments
Labels
Build Issue Issues related to build or environment problems on any platform. good first issue Standard label for new developers to locate good issues to tackle to learn about OCIO development. help wanted Issues that the TSC has decided are worth implementing, but don't currently have the dev resources.

Comments

@cary-ilm
Copy link
Member

cary-ilm commented Sep 2, 2024

The OpenSSF Best Practices Badge suggests signing release artifacts, using OpenEXR's release-sign.yml workflow as a template. It's triggered on release creation and does these steps:

  1. Runs get archive to generate a <release>.tar.gz artifact
  2. Signs the <release>.tar.gz via sigstore
  3. Uploads the resulting sigstore signature file along with the tarball.
@doug-walker doug-walker added good first issue Standard label for new developers to locate good issues to tackle to learn about OCIO development. Build Issue Issues related to build or environment problems on any platform. labels Sep 3, 2024
@carolalynn carolalynn added the help wanted Issues that the TSC has decided are worth implementing, but don't currently have the dev resources. label Sep 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Build Issue Issues related to build or environment problems on any platform. good first issue Standard label for new developers to locate good issues to tackle to learn about OCIO development. help wanted Issues that the TSC has decided are worth implementing, but don't currently have the dev resources.
Projects
None yet
Development

No branches or pull requests

3 participants