You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ensure that Pinniped's dependencies have been upgraded, to the extent desired by the team (refer to the diff output from the latest run of the all-golang-deps-updated CI job)
If you are updating golang in Pinniped, be sure to update golang in CI as well. Do a search-and-replace to update the version number everywhere in the pinniped ci branch.
If the Fosite library is being updated and the format of the content of the Supervisor's storage Secrets are changed, or if any change to our own code changes the format of the content of the Supervisor's session storage Secrets, then be sure to update the accessTokenStorageVersion, authorizeCodeStorageVersion, oidcStorageVersion, pkceStorageVersion, refreshTokenStorageVersion, variables in files such as internal/fositestorage/accesstoken/accesstoken.go. Failing tests should signal the need to update these values.
For go.mod direct dependencies that are v2 or above, such as github.com/google/go-github/vXX, check to see if there is a new major version available. Try using hack/update-go-mod/update-majors.sh.
The main pipeline is green, up to and including the ready-to-release job. Check that the expected git commit has passed the ready-to-release job.
Optional: a blog post for the release is written and submitted as a PR but not merged yet
All merged user stories are accepted (manually tested)
Only after all stories are accepted, manually trigger the release job to create a draft GitHub release
Manually edit the draft release notes on the GitHub release to describe the contents of the release, using the format which was automatically added to the draft release
Publish (i.e. make public) the draft release
After making the release public, the jobs in the main pipeline beyond the release job should auto-trigger, so check to make sure that they passed
Edit the blog post's date to make it match the actual release date, and merge the blog post PR to make it live on the website
Publicize the release via tweets, etc.
Close this issue
The text was updated successfully, but these errors were encountered:
Release checklist
ci
branch.accessTokenStorageVersion
,authorizeCodeStorageVersion
,oidcStorageVersion
,pkceStorageVersion
,refreshTokenStorageVersion
, variables in files such asinternal/fositestorage/accesstoken/accesstoken.go
. Failing tests should signal the need to update these values.github.com/google/go-github/vXX
, check to see if there is a new major version available. Try usinghack/update-go-mod/update-majors.sh
.replace
directives in thego.mod
file. Are they up to date versions? Can anyreplace
directives be removed?k8s-code-generator
CI job definitions are up-to-date with the latest Go, K8s, andcontroller-gen
versionsready-to-release
job. Check that the expected git commit has passed theready-to-release
job.Optional: a blog post for the release is written and submitted as a PR but not merged yetrelease
job to create a draft GitHub releaseEdit the blog post's date to make it match the actual release date, and merge the blog post PR to make it live on the websiteThe text was updated successfully, but these errors were encountered: