Changing name of column does not generate a database migration

[perlDreamer]

In ving_maintenance, I changed the column name from jobsId to cronJobId, along with the relationship information. Running:

ving.mjs drizzle --prepare gave me this output;

drizzle-kit: v0.20.13
drizzle-orm: v0.29.5

Reading schema files:
/Users/colinkuskie/TGCv/ving/drizzle/schema/APIKey.mjs
/Users/colinkuskie/TGCv/ving/drizzle/schema/CronJob.mjs
/Users/colinkuskie/TGCv/ving/drizzle/schema/HardwareItem.mjs
/Users/colinkuskie/TGCv/ving/drizzle/schema/HardwareItemSet.mjs
/Users/colinkuskie/TGCv/ving/drizzle/schema/HardwareSchedule.mjs
/Users/colinkuskie/TGCv/ving/drizzle/schema/HardwareTask.mjs
/Users/colinkuskie/TGCv/ving/drizzle/schema/HardwareTicket.mjs
/Users/colinkuskie/TGCv/ving/drizzle/schema/HardwareTicketFile.mjs
/Users/colinkuskie/TGCv/ving/drizzle/schema/HardwareTicketRemark.mjs
/Users/colinkuskie/TGCv/ving/drizzle/schema/S3File.mjs
/Users/colinkuskie/TGCv/ving/drizzle/schema/User.mjs

11 tables
apikeys 8 columns 0 indexes 1 fks
cronjobs 8 columns 0 indexes 0 fks
hardwareitems 6 columns 0 indexes 1 fks
hardwareitemsets 7 columns 0 indexes 0 fks
hardwareschedules 11 columns 0 indexes 2 fks
hardwaretasks 5 columns 0 indexes 1 fks
hardwaretickets 11 columns 0 indexes 2 fks
hardwareticketfiles 5 columns 0 indexes 2 fks
hardwareticketremarks 8 columns 0 indexes 1 fks
s3files 12 columns 0 indexes 1 fks
users 18 columns 3 indexes 1 fks

No schema changes, nothing to migrate 😴

This seems bad?

[perlDreamer]

I didn't create the tables first.