Skip to content

Latest commit

 

History

History
19 lines (16 loc) · 1.31 KB

RELEASE.md

File metadata and controls

19 lines (16 loc) · 1.31 KB

Release Process

  1. Merge all PRs intended for the release.
  2. Rebase latest remote main branch locally (git pull --rebase origin main).
  3. Ensure all analysis checks and tests are passing (time TEST_COMPUTE_INIT=1 TEST_COMPUTE_BUILD=1 TEST_COMPUTE_DEPLOY=1 make all).
  4. Ensure goreleaser builds locally (make fastly GORELEASER_ARGS="--skip-validate --skip-post-hooks --clean").
  5. Open a new PR to update CHANGELOG (example)1.
  6. Merge CHANGELOG.
  7. Rebase latest remote main branch locally (git pull --rebase origin main).
  8. Tag a new release (tag=vX.Y.Z && git tag -s $tag -m "$tag" && git push origin $tag)2.
  9. Copy/paste CHANGELOG into the draft release.
  10. Publish draft release.
  11. Communicate the release in the relevant Slack channels3.

Footnotes

  1. We utilize semantic versioning and only include relevant/significant changes within the CHANGELOG.
  2. Triggers a github action that produces a 'draft' release.
  3. Fastly make internal announcements in the Slack channels: #api-clients, #ecp-languages.