1# When gqlgen gets released, the following things need to happen
2Assuming the next version is $NEW_VERSION=v0.16.0 or something like that.
3
41. Run the https://github.com/99designs/gqlgen/blob/master/bin/release:
5```
6./bin/release $NEW_VERSION
7```
82. git-chglog -o CHANGELOG.md
93. go generate ./...; cd _examples; go generate ./...; cd ..
104. git commit and push the CHANGELOG.md
115. Go to https://github.com/99designs/gqlgen/releases and draft new release, autogenerate the release notes, and Create a discussion for this release
126. Comment on the release discussion with any really important notes (breaking changes)
13
14I 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.
15
View as plain text