Mirrors/stash
1
0
Fork 0
mirror of https://github.com/stashapp/stash.git synced 2025-12-16 20:07:05 +03:00
Code Issues Packages Projects Releases Wiki Activity
Files
30809e16faea26ddbcaa726c7b5119cd246100b3
stash/vendor/github.com/99designs/gqlgen/RELEASE-CHECKLIST.md
WithoutPants 30809e16fa Update go dependencies (#3480) 
* Bump golang.org/x/text from 0.3.7 to 0.3.8

Bumps [golang.org/x/text](https://github.com/golang/text) from 0.3.7 to 0.3.8.
- [Release notes](https://github.com/golang/text/releases)
- [Commits](https://github.com/golang/text/compare/v0.3.7...v0.3.8)

---
updated-dependencies:
- dependency-name: golang.org/x/text
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>

* Update go dependencies

* Update x/net

---------

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-02-28 08:26:14 +11:00

796 B
Raw Blame History

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.