Skip to content

Conversation

acwhite211
Copy link
Member

@acwhite211 acwhite211 commented Oct 6, 2025

Fixes #7448

Fixes outstanding schema changes in the django models that haven't been added to the migrations yet.

If you encounter the issue:

Your models in app(s): 'specify' have changes that are not yet reflected in a migration, and so won't be applied.
Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them.

then run the following commands:

ve/bin/python manage.py migrate specify 0039 --fake;
ve/bin/python manage.py migrate;

Checklist

  • Self-review the PR after opening it to make sure the changes look good and
    self-explanatory (or properly documented)
  • Add relevant issue to release milestone
  • Add pr to documentation list

Testing instructions

  • Startup instance on the branch and check the logs to make sure no errors occurred during the migration processes. If a warning appears related ".. not yet reflected in a migration", then see the commands in the description. Make sure no other errors occur.

@acwhite211 acwhite211 added this to the 7.12.0 milestone Oct 6, 2025
@acwhite211 acwhite211 self-assigned this Oct 6, 2025
@github-project-automation github-project-automation bot moved this to 📋Back Log in General Tester Board Oct 6, 2025
@acwhite211 acwhite211 marked this pull request as ready for review October 6, 2025 20:51
@acwhite211 acwhite211 requested review from a team October 6, 2025 20:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: 📋Back Log

Development

Successfully merging this pull request may close these issues.

Startup warning due to missing Django migration for 'specify' app

1 participant