Migration doesn't work automatically

[llamafilm]

After upgrading this plugin from 0.5.6 to 0.6.0, all my branches were unusable, showing as "pending migrations". Even though I did run the manage.py migrate and got this output:

Applying database migrations ...
Operations to perform:
  Apply all migrations: account, auth, circuits, contenttypes, core, dcim, django_rq, extras, ipam, netbox_attachments, netbox_branching, sessions, social_django, taggit, tenancy, users, virtualization, vpn, wireless
Running migrations:
  Applying netbox_branching.0005_branch_applied_migrations... OK

It was straightforward to fix, I just clicked the Migrate button and it worked. I'm just surprised this was necessary — especially because the message displayed shows the same name as the migration which was supposedly already done in the shell.

[dionrowney]

I have noticed this also, except my Migrate button is greyed out and unable to select it.

[jeremystretch]

This is working as intended. Each branch must be migrated independently.

[dionrowney]

I understand why this needed as the schema is basically a clone of the database but How is this done if the migrate button is not clickable and the commandline only migrates the main database ? Dion

…

On Mon, Aug 4, 2025, 06:20 Jeremy Stretch ***@***.***> wrote: This is working as intended. Each branch must be migrated independently. — Reply to this email directly, view it on GitHub <#303 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOUPTP4QTHGZUJWFMGHOAXL3L5F2FAVCNFSM6AAAAACCJMIIV6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGOJYHAYTONQ> . You are receiving this because you are subscribed to this thread.Message ID: <netboxlabs/netbox-branching/repo-discussions/303/comments/13988176@ github.com>

[dionrowney]

It seems that the pending migrations only is an active button when an un-merged branch that was unmerged during an upgrade is present.

I had a previously merged branch in the list and it had that warning as well but it wasn't allowing the migrations on it, even though I would have though that the migrations would have to get done on that schema as well. I was able to revert that previous branch also and the migrate button still remained unclickable.

Im not sure if this is the expected behaviour but I didnt run into issues either.

I am guessing one should ensure all branches are closed and deleted before upgrading just to avoid unexpected issues. The upgrade process and warnings seems to be missing from the REAME and the best practices may be helpful there.