Skip to content

Latest commit

 

History

History
20 lines (17 loc) · 1.28 KB

RELEASE.md

File metadata and controls

20 lines (17 loc) · 1.28 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 (make all).
  4. Open a new PR to update CHANGELOG (example)1,2,3.
  5. Merge CHANGELOG.
  6. Rebase latest remote main branch locally (git pull --rebase origin main).
  7. Tag a new release (tag=vX.Y.Z && git tag -s $tag -m "$tag" && git push origin $tag).
  8. Copy/paste CHANGELOG into a new draft release4.
  9. Publish draft release.
  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. Also bump ProjectVersion in fastly/client.go.
  3. If a major version change, then update references to the version in go.mod and README.md.
  4. Use the format: vX.Y.Z - yyyy-mm-dd for the release title.
  5. Fastly make internal announcements in the Slack channels: #api-clients, #ecp-languages.