Cam Hutchison
fd593b63ba
Update the preflight docs to provide instructions for building the buildboxes for the new version that master becomes. The buildboxes build on a schedule and that can mean up to a week will need to pass before the buildboxes are automatically built, given that the assets buildbox is build only once a week (Sundays) and that is needed to build the centos7 buildboxes. The updated instructions describe how to kick off that build automatically.
1.5 KiB
Preflight Checklist
This checklist is to be run prior to cutting the release branch.
- Bump Web UI dependencies
- Make a new docs/VERSION folder
- Update VERSION in Makefile to next dev tag
- Update TELEPORT_VERSION in assets/aws/Makefile
- Update
base-refto point to the new release branch in.github/workflows/dependency-review.yaml - Update mentions of the version in examples/ and README.md
- Search code for DELETE IN and REMOVE IN comments and clean up if appropriate
- Update docs/faq.mdx "Which version of Teleport is supported?" section with release date and support info
- Update the CI buildbox image
-
Update the
BUILDBOX_VERSIONinbuild.assets/images.mk. Commit and merge. -
Update
e/.github/workflows/build-buildboxes-cron.yamlto uncomment final pre-release job and ensure it has the correct branch names (two places). Commit and merge. -
After the
BUILDBOX_VERSIONupdate in thebuild.assets/images.mkhas merged to master, build the buildboxes for the nextBUILDBOX_VERSION. The first run will build the "assets" buildbox and the other builds will likely fail. Run again after the first has finished to build the others that use the "assets" buldbox:today=$(LOCALE=C TZ=UTC date +%A) gh workflow run --repo gravitational/teleport.e --field assets-day="${today}" build-buildboxes.yaml gh workflow run --repo gravitational/teleport.e build-buildboxes.yaml
-