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

Consider adopting signed release tags #1856

Closed
cary-ilm opened this issue Sep 2, 2024 · 0 comments · Fixed by #1911
Closed

Consider adopting signed release tags #1856

cary-ilm opened this issue Sep 2, 2024 · 0 comments · Fixed by #1911

Comments

@cary-ilm
Copy link
Member

cary-ilm commented Sep 2, 2024

The OpenSSF Best Practices Badge suggests signing release tags. The process is simple, described here: simply create the release from a tag created with -s:

$ git tag -s v1.2.3

The project maintainer who creates the release tags needs a GPG key. Instructions for creating a key are described here.
lgritz added a commit to lgritz/OpenShadingLanguage that referenced this issue Jan 2, 2025
@lgritz
docs: Improve release related docs
84db608 
* Move RELEASING.md into the dev docs area
* Document signed release tags, which we will start doing now
* Document release note generation
* Add git-cliff config file
* Update SECURITY version documentation

Closes AcademySoftwareFoundation#1856

Signed-off-by: Larry Gritz <lg@larrygritz.com>
@lgritz lgritz mentioned this issue Jan 2, 2025
Merged
@lgritz lgritz closed this as completed in b6055bf Jan 2, 2025
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

Successfully merging a pull request may close this issue.

docs: Improve release related docs lgritz/OpenShadingLanguage
1 participant
@cary-ilm