Suvethan的回答是正确的，但是迁移代码片段中有一个小错误. Sequelize迁移期望返回一个承诺，这在生成的迁移框架的注释中指出:

Suvethan's answer is correct, but the migration code snippet has a minor bug. Sequelize migrations expect a promise to be returned, which is noted in a comment in the generated migration skeleton:

Add altering commands here.
Return a promise to correctly handle asynchronicity.

Example:
return queryInterface.createTable('users', { id: Sequelize.INTEGER });

因此，返回一组承诺可能会导致意外结果，因为无法保证在继续下一次迁移之前，所有的承诺都将得到解决.对于大多数操作，您几乎不会遇到任何问题，因为大多数事情将在Sequelize关闭该过程之前完成.但是，我认为在进行数据库迁移时要比后悔更安全.您仍然可以利用承诺的数组.您只需要将其包装在Promise.all调用中即可.

So, returning an array of promises can potentially lead to unexpected results because there's no guarantee that all of the promises will have resolved before moving on to the next migration. For most operations you're unlikely to run into any issues since most things will complete before Sequelize closes the process. But I think it's better to be safe than sorry when it comes to database migrations. You can still leverage the array of promises; you just need to wrap it in a Promise.all call.

Suvethan的示例，但带有Promise.all:

module.exports = {
  up: function (queryInterface, Sequelize) {
    return Promise.all([
      queryInterface.addColumn(
        'Users',
        'gender',
         Sequelize.STRING
       ),
      queryInterface.addColumn(
        'Users',
        'age',
        Sequelize.STRING
      )
    ]);
  },

  down: function (queryInterface, Sequelize) {
    // logic for reverting the changes
  }
};