Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set graphql-core-next as v3 of graphql-core #40

Merged
merged 4 commits into from
Jul 13, 2019
Merged

Set graphql-core-next as v3 of graphql-core #40

merged 4 commits into from
Jul 13, 2019

Conversation

mvanlonden
Copy link
Member

This repository will build and distribute the graphql-core package starting at version 3.

graphql/version.py Outdated Show resolved Hide resolved
.travis.yml Outdated Show resolved Hide resolved
.bumpversion.cfg Outdated
@@ -1,5 +1,5 @@
[bumpversion]
current_version = 3.0.0
current_version = 3.0.0-alpha
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right, we definitely need to publish some alphas and betas before 3.0 final.

But I think it should be 3.0.0a0 (PEP 440).

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will make that change

@Cito
Copy link
Member

Cito commented Jun 30, 2019

Before making the jump from "Core-Next 1.0.5" to "Core 3.0.0", we should have a working prototype of Graphene 3 in order to be sure we have all necessary functionality (like #41 and #42). I also want to release one last version Core-Next 1.0.6 which prints a deprecation warning and points to Core 3.0.0.

@Cito Cito added the pending Waiting for other issues to move forward label Jun 30, 2019
@Cito Cito removed the pending Waiting for other issues to move forward label Jul 13, 2019
@Cito Cito merged commit a8ec2a9 into master Jul 13, 2019
@Cito
Copy link
Member

Cito commented Jul 14, 2019

Unfortunately, uploading with these deploy credentials failed. Can you verify that "travis encrypt" was been executed in the right directory?

@Cito Cito deleted the v3-release branch July 17, 2019 13:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants