-
Notifications
You must be signed in to change notification settings - Fork 170
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
Migrations not up 2 date #70
Labels
Comments
Merged
Hi @onceatime !, Thanks. |
@onceatime thanks! |
tim-schilling
pushed a commit
to tim-schilling/django-graphql-jwt
that referenced
this issue
Jan 10, 2022
Bumps [django](https://github.com/django/django) from 3.2.6 to 3.2.7. - [Release notes](https://github.com/django/django/releases) - [Commits](django/django@3.2.6...3.2.7) --- updated-dependencies: - dependency-name: django dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
when we run makemigrations a new migration in /graphql_jwt/refresh_token/migrations/0002_auto_20190123_1648.py gets created with the following content:
in ci we check if any uncreated migrations exist. if yes it stops the deployment. This happens because.
in https://github.com/flavors/django-graphql-jwt/blob/v0.2.0/graphql_jwt/refresh_token/migrations/0001_initial.py
but in https://github.com/flavors/django-graphql-jwt/blob/v0.2.0/graphql_jwt/refresh_token/models.py
The text was updated successfully, but these errors were encountered: