You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 25, 2024. It is now read-only.
1. Ensure you are running on the oldest supported Elixir version (check `.travis.yml`)
6
+
7
+
2. Ensure `CHANGELOG.md` is updated and add current date
8
+
9
+
3. Change the version number in `mix.exs` and `README.md`
10
+
11
+
4. Run `mix test` to ensure all tests pass
12
+
13
+
5. Commit changes above with title "Release vVERSION" and push to GitHub
14
+
15
+
git add .
16
+
git commit -m"Release vX.Y.Z"
17
+
git push origin master
18
+
19
+
6. Check CI is green
20
+
21
+
7. Create a release on GitHub and add the CHANGELOG from step #2 (https://github.com/graphql-elixir/plug_graphql/releases/new) using VERSION as the tag and title
22
+
23
+
8. Publish new hex release with `mix hex.publish`
24
+
25
+
9. Publish hex docs with `mix hex.docs`
26
+
27
+
10. Update upstream repos `hello_graphql_phoenix` and `graphql_relay` and release as appropriate
28
+
29
+
## Deprecation policy
30
+
31
+
GraphQL deprecations happen in 3 steps:
32
+
33
+
1. The feature is soft-deprecated. It means both CHANGELOG and documentation must list the feature as deprecated but no warning is effectively emitted by running the code. There is no requirement to soft-deprecate a feature.
34
+
35
+
2. The feature is effectively deprecated by emitting warnings on usage. In order to deprecate a feature, the proposed alternative MUST exist for AT LEAST two versions.
36
+
37
+
3. The feature is removed. This can only happen on major releases.
0 commit comments