Migrations
What database migrations are and how to run them from the admin panel after a deployment.
Database migrations apply schema changes to herbe.calendar's database. They run automatically on most deployments, but occasionally a migration requires manual confirmation from the admin panel.
What "pending" means
If the admin panel shows a banner saying there are pending migrations, one or more schema changes have been deployed but not yet applied to the database. The calendar may behave unexpectedly or show errors until they are run.
Running migrations
Go to Admin → Migrations.
The screen lists each pending migration with its name and a short description of what it changes. Review the list, then click Run pending migrations. Migrations run in order and cannot be skipped individually.
Once complete, the list clears and a timestamp shows when each migration was last applied.
When to run migrations
Only after a deployment that includes schema changes. herbe.calendar's release notes or your administrator's update instructions will say when this is needed. For day-to-day admin work, this screen requires no attention.
If a migration fails
A failed migration stops the sequence — later migrations do not run. The error message on screen describes what went wrong. Common causes include insufficient database permissions or a constraint conflict from existing data. Contact the deployment team with the full error text.