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.

Sign up for GitHub

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

Jump to bottom

Update signing capability to sign GitHub Releases #258

Open
Miranlfk opened this issue Jun 2, 2023 · 1 comment
Open

Update signing capability to sign GitHub Releases #258

Miranlfk opened this issue Jun 2, 2023 · 1 comment

Comments

@Miranlfk
Copy link

Miranlfk commented Jun 2, 2023 •
edited

Current Behavior -
Release binaries/artifacts must be pushed to an OCI compatible registry beforehand and thereafter notation can sign it.

Proposed Improvement -
Investigate in enhancing Notation signing capability to sign releases/binaries/artifacts published on GitHub Releases. In general release artifacts/binaries would be published in GitHub Releases, therefore supporting this capability can promote adoption better.
@toddysm
Copy link
Contributor

toddysm commented Jul 19, 2023

I believe this is similar to notaryproject/notation#741

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@toddysm @Miranlfk