-
Notifications
You must be signed in to change notification settings - Fork 79
Release checklist for v0.36.0 #2148
Copy link
Copy link
Closed
Description
Release checklist
- 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
cibranch. - 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 asinternal/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. - Evaluate all
replacedirectives in thego.modfile. Are they up to date versions? Can anyreplacedirectives be removed?
- 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
- Ensure that Pinniped's codegen is up-to-date with the latest Kubernetes releases by making sure this file is updated compared to the latest releases listed here for active branches and here for non-active branches
- Ensure that the
k8s-code-generatorCI job definitions are up-to-date with the latest Go, K8s, andcontroller-genversions- See 9960c80
- All relevant feature and docs PRs are merged
- One more dependency bump: Bump dependencies #2150
- The main pipeline is green, up to and including the
ready-to-releasejob. Check that the expected git commit has passed theready-to-releasejob. - All merged user stories are accepted (manually tested)
- Only after all stories are accepted, manually trigger the
releasejob 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
- Publicize the release via tweets, etc.
- Close this issue
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels