Some checks failed
Deploy to production / deploy (push) Has been cancelled
- Modified the deployment workflow to include new migration paths for the backend, ensuring that migrations are correctly referenced in the deployment process. - Updated the `db:migrate` script in package.json to point to the `migrations-active` directory, enhancing clarity and organization of migration files. - Adjusted the deployment conditions to account for changes in migration file locations, improving the accuracy of change detection during deployments. - Removed obsolete migration files to streamline the migration process and prevent confusion.
30 lines
537 B
JavaScript
30 lines
537 B
JavaScript
'use strict';
|
|
|
|
module.exports = {
|
|
up: async (queryInterface, Sequelize) => {
|
|
await queryInterface.addColumn(
|
|
{
|
|
tableName: 'falukant_user',
|
|
schema: 'falukant_data'
|
|
},
|
|
'last_nobility_advance_at',
|
|
{
|
|
type: Sequelize.DATE,
|
|
allowNull: true
|
|
}
|
|
);
|
|
},
|
|
|
|
down: async (queryInterface, Sequelize) => {
|
|
await queryInterface.removeColumn(
|
|
{
|
|
tableName: 'falukant_user',
|
|
schema: 'falukant_data'
|
|
},
|
|
'last_nobility_advance_at'
|
|
);
|
|
}
|
|
};
|
|
|
|
|