opensource/teleport
3
0
Fork 0
mirror of https://github.com/gravitational/teleport.git synced 2026-11-03 15:41:57 +08:00
Code Issues Packages Projects Releases Wiki Activity
Files
86efc77e042cc2a00a2da87559bf164a1e6910b2
teleport/docs/postrelease.md
T
Reed Loden e2d69aedde Post-major version release activities (#37676) 
From `docs/postrelease.md`:
- [x] Update `branchMajorVersion` const in Dronegen `/dronegen/container_images.go`, then run `make dronegen`
- [x] Update `CURRENT_VERSION_ROOT`, `PREVIOUS_VERSION_ONE_ROOT`, and `PREVIOUS_VERSION_TWO_ROOT` variables in `.drone.yml`, then run `make dronegen`
  - Example: https://github.com/gravitational/teleport/pull/4602
- [x] Create PR to update default Teleport image referenced in docker/teleport-quickstart.yml
  - Example: https://github.com/gravitational/teleport/pull/4655
- [x] Create PR to update default Teleport image referenced in docker/teleport-lab.yml
2024-02-01 22:08:58 +00:00

1.6 KiB
Raw Blame History

Post-release Checklist

This checklist is to be run after cutting a release.

All releases

Our GitHub Actions workflows will create two PRs when a release is published:

  1. A PR against the release branch that updates the default version in our docs.
  2. A PR that updates the AWS AMI IDs for the new release. (This job only runs for releases on the latest release branch)

The AWS AMI ID PR can be merged right away.

The docs version PR should be merged after the gravitational/teleport-plugins release is published, since the PR will include an update to the plugins version as well.

Major releases only

Reference in New Issue View Git Blame Copy Permalink