-
Notifications
You must be signed in to change notification settings - Fork 28
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
fix: django.contrib.postgres.fields.JSONField causes an error in Django 4.2 (fields.E904) https://docs.djangoproject.com/en/4.2/ref/checks/ #154
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jpmckinney would you mind fixing the tests?
For example: env \ GEOS_LIBRARY_PATH='/opt/homebrew/opt/geos/lib/libgeos_c.dylib' \ GDAL_LIBRARY_PATH='/opt/homebrew/opt/gdal/lib/libgdal.dylib' \ DATABASE_DB=opencivicdata_test \ DATABASE_USER=myuser \ DATABASE_PASSWORD= \ PYTHONPATH=. pytest --ds=opencivicdata.tests.test_settings
@fgregg All green now. |
thanks for this, @jpmckinney. hope all is well with you |
All good here :) It looks like the commit to roll the version to 3.3.1 is not on master. It was also tagged a "v3.3.1" (like v3.3.0). However, the other tags omit the "v". Okay for me to tag and release as "3.4.0" ? |
go for it! |
Ah, I see why the "v" was included - the workflow only runs on "v*" tags. I'll use it. |
No description provided.