AutoMigrate VS golang-migrate

[SpikeWong]

In my previous work experience, we usually used versioned migration tools like golang-migrate to manage and execute migrate files, and we would have a dedicated runner to perform migrate operations. But I'm currently working on a project that uses gorm's automigrate when the api server is started, so I'm wondering

1. the pros and cons of using a dedicated runner as opposed to executing migrate on api server startup
2. the pros and cons of using golang-migrate compared to using AutoMigrate

[SpikeWong]

For the first point, what I can think of is that if we migrate while the api server is starting up, and the api server is not yet ready, but the migrate is in progress, the request may not be responded to.
For the second point, a tool like golang-migrate can perform down operations and can delete unused tables and columns.

Hope to get more opinions. :)