-
Notifications
You must be signed in to change notification settings - Fork 908
chore(actions): Add attestation URL, download and verify commands on release notes #2982
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
base: main
Are you sure you want to change the base?
chore(actions): Add attestation URL, download and verify commands on release notes #2982
Conversation
chore(actions): Add post release workflow
Update post-relese-smoke-tests.yaml
Update CHANGELOG.md
|
👋 Hi! Thank you for this contribution! Just to let you know, our GitHub SDK team does a round of issue and PR reviews twice a week, every Monday and Friday! We have a process in place for prioritizing and responding to your input. Because you are a part of this community please feel free to comment, add to, or pick up any issues/PRs that are labeled with |
Signed-off-by: Viacheslav Kudinov <viacheslav@kudinov.tech>
b3823bf to
3580ffc
Compare
|
Hi @nickfloyd |
stevehipwell
left a comment
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.
This pattern means that release notifications wont contain the attestation text as it's appended after the release. My suggestion would either be to link to docs on how to validate or to use custom release notes.
Resolves #ISSUE_NUMBER
Before the change?
After the change?
Example: https://github.com/vk-or/terraform-provider-github/releases/tag/v0.0.18
Pull request checklist
Does this introduce a breaking change?
Please see our docs on breaking changes to help!