graphql-python / graphql-python/graphql-core-legacy

☂️GraphQL-core v3

オープン
#249 コメント 3 件 リアクション 6 件 担当者 0 名 GitHub で見る
主要言語
Python
スター
372
フォーク
175
PR マージ指標
30日以内にマージされた PR はありません

説明

We will shortly be publishing [GraphQL-core-next](https://github.com/graphql-python/graphql-core-next) as v3 of GraphQL-core. There are breaking changes as part of this release and so this issue is to track all the tasks needed to get the ecosystem ready for the upgrade.

# Publish Graphql-core v3

* [x] Make graphql-relay-py next branch compatible with core-next
* [x] Make graphene next branch compatible with core-next
* [x] Create [v2 of graphql-relay-py](https://github.com/graphql-python/graphql-relay-py/pull/21) (compatible with core v2) on PyPI
* [x] Bring graphql-core-next up to date with GraphQL.js 14.4
* [x] Close open issues of graphql-core-next as far as possible
* [x] Setup graphql-core-next repo to publish as graphql-core: https://github.com/graphql-python/graphql-core-next/pull/40
* [x] Publish v2 of graphql-relay-py on PyPI (needs maintainer rights from Syrus)
* [x] Bring graphql-relay-py [next](https://github.com/graphql-python/graphql-relay-py/tree/next) branch up-to-date with graphql-relay-js 0.6 and add type hints
* [x] Make graphql-relay-py [next](https://github.com/graphql-python/graphene/tree/next/feature/core-next) branch the new master, move old master to legacy branch
* [x] Publish v3.0.0.a0 of graphql-relay-py on PyPI
* [x] Publish last version of graphql-core-next on PyPI
* [x] Create legacy branch of graphq-core-next from master
* [x] Change distribution name and version of GraphQL-core-next to GraphQL-core and set version to 3.0.0a0 in master branch
* [x] Publish GraphQL-core 3.0.0a0 on PyPI
* [x] Add notice to old graphql-core repository README that this is now deprecated
* [x] Make sure automatic deployment of GraphQL-core 3 on new tags works
* [x] Publish v3.0.0.b0 of graphql-relay-py and graphql-core
* [x] Publish v3.0.0 final of graphql-relay-py and graphql-core

# Pin dependant packages (not blocking)

* [x] [Graphene](https://github.com/graphql-python/graphene)
* [x] [GraphQL-server-core](https://github.com/graphql-python/graphql-server-core)
* [x] [GraphQL WS](https://github.com/graphql-python/graphql-ws)
* [x] [GraphQL-relay](https://github.com/graphql-python/graphql-relay-py) https://github.com/graphql-python/graphql-relay-py/pull/20
- [x] Master up to date
- [x] New release published
* [x] [GQL](https://github.com/graphql-python/gql) https://github.com/graphql-python/gql/pull/47
* [ ] [aiohttp-graphql](https://github.com/graphql-python/aiohttp-graphql) https://github.com/graphql-python/aiohttp-graphql/pull/11
- [x] Master up to date
- [ ] New release published
* [ ] [flask-graphql](https://github.com/graphql-python/flask-graphql) https://github.com/graphql-python/flask-graphql/pull/60
- [x] Master up to date
- [ ] New release published
* [ ] [sanic-graphql](https://github.com/graphql-python/sanic-graphql) https://github.com/graphql-python/sanic-graphql/pull/17
- [ ] Master up to date
- [ ] New release published
* [ ] [webob-graphql](https://github.com/graphql-python/webob-graphql) https://github.com/graphql-python/webob-graphql/pull/8
- [ ] Master up to date
- [ ] New release published
* [x] [dagit](https://github.com/dagster-io/dagster/blob/master/python_modules/dagit/setup.py) https://github.com/dagster-io/dagster/pull/1549

# Clean-up (not blocking)

* [ ] Make gql-next work with core v3.0.0
* [ ] Rename gql to gql-legacy and gql-next to gql, or merge gql-next into gql
* [ ] Rename graphql-core to graphql-core-legacy and graphql-core-next to graphql-core, or merge graphql-core-next into graphql-core, see #241

コントリビューションガイド

このリポジトリのコントリビューションガイドは索引されていません

調査の方向性

Start with the unchecked checklist items for aiohttp-graphql, flask-graphql, sanic-graphql, webob-graphql, gql, and the repository rename tasks; the linked external pull requests provide the current context. Done means confirming the remaining package releases and cleanup work, but this tracking issue has no single file, test, or entry point to begin from.

索引モデルが issue の本文から書いたものです。

評価

技術スタック
python
領域
api, release
issue の種類
機能追加
難易度
5/5
見積もり時間
1週間以上
活発さ
停滞
明瞭さ
説明が足りない
初心者へのやさしさ
15/100

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。