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

fixed nautobot v2.3.0 compatibility #361

Merged
merged 3 commits into from
Aug 7, 2024

Conversation

gsnider2195
Copy link
Contributor

@gsnider2195 gsnider2195 commented Aug 7, 2024

Closes #360

@progala
Copy link
Contributor

progala commented Aug 7, 2024

@gsnider2195 Can you tell me what are those migrations for? I have a number of new migrations in next3.0 so would like to understand how to integrate them.

@gsnider2195
Copy link
Contributor Author

Django 4 changed the way it generates migrations so it's no longer interpreting the related_name of model fields when generating migration files. These migrations are a no-op but are required to suppress the warnings in Django 4.

@progala
Copy link
Contributor

progala commented Aug 7, 2024

Got it, thanks!

@gsnider2195 gsnider2195 merged commit 18aab02 into develop Aug 7, 2024
15 checks passed
@gsnider2195 gsnider2195 deleted the u/gas-360-django4-nautobot2.3 branch August 7, 2024 18:53
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.

Fix incompatibilities with Nautobot v2.3.0 beta1
3 participants