Skip to content

Latest commit

 

History

History
15 lines (12 loc) · 796 Bytes

RELEASE-CHECKLIST.md

File metadata and controls

15 lines (12 loc) · 796 Bytes
Raw

When gqlgen gets released, the following things need to happen

Assuming the next version is $NEW_VERSION=v0.16.0 or something like that.

  1. Run the https://github.com/99designs/gqlgen/blob/master/bin/release:
./bin/release $NEW_VERSION
  1. git-chglog -o CHANGELOG.md
  2. go generate ./...; cd _examples; go generate ./...; cd ..
  3. git commit and push the CHANGELOG.md
  4. Go to https://github.com/99designs/gqlgen/releases and draft new release, autogenerate the release notes, and Create a discussion for this release
  5. Comment on the release discussion with any really important notes (breaking changes)

I used https://github.com/git-chglog/git-chglog to automate the changelog maintenance process for now. We could just as easily use go releaser to make the whole thing automated.