Skip to content
This repository has been archived by the owner on Feb 21, 2023. It is now read-only.

Latest commit

 

History

History
20 lines (17 loc) · 1.63 KB

RELEASE.md

File metadata and controls

20 lines (17 loc) · 1.63 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 (TEST_PARALLELISM=8 make testacc).
  4. Open a new PR to update CHANGELOG (example)1.
  5. Merge CHANGELOG.
  6. Rebase latest remote main branch locally (git pull --rebase origin main)2.
  7. Tag a new release (tag=vX.Y.Z && git tag -s $tag -m "$tag" && git push origin $tag)3.
  8. Copy/paste CHANGELOG into the draft release.
  9. Publish draft release4.
  10. Communicate the release in the relevant Slack channels5.

Footnotes

  1. We utilize semantic versioning and only include relevant/significant changes within the CHANGELOG.
  2. Manually update generated docs/index.md and force push (as we're not able to update the git tag until the next step).
  3. Triggers a github action that produces a 'draft' release.
  4. Triggers a github webhook that produces a release on the terraform registry.
  5. Fastly make internal announcements in the Slack channels: #api-clients, #ecp-languages.