Skip to content

Latest commit

 

History

History
18 lines (15 loc) · 1.48 KB

RELEASE.md

File metadata and controls

18 lines (15 loc) · 1.48 KB

Release Process

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

Footnotes

  1. We utilize semantic versioning and only include relevant/significant changes within the CHANGELOG (be sure to document changes to the app config if config_version has changed, and if any breaking interface changes are made to the fastly.toml manifest those should be documented on https://fastly.com/documentation/developers).
  2. Triggers a github action that produces a 'draft' release.