fix: make sure migration triggers with the correct date for current development

pull/2660/head
William Grant 2 years ago
parent df40ff8855
commit 61b91e2485

@ -1226,8 +1226,8 @@ function updateToSessionSchemaVersion30(currentVersion: number, db: BetterSqlite
db.prepare(`ALTER TABLE ${CONVERSATIONS_TABLE} ADD COLUMN hasOutdatedClient TEXT;`).run();
// TODO update to agreed value between platforms
const disappearingMessagesV2ReleaseTimestamp = 1677488400000; // unix 27/02/2023 09:00
// const disappearingMessagesV2ReleaseTimestamp = 1677661200000; // unix 01/03/2023 09:00
const disappearingMessagesV2ReleaseTimestamp = 1680339600000; // unix 01/04/2023 09:00
// const disappearingMessagesV2ReleaseTimestamp = 1677488400000; // unix 27/02/2023 09:00
// support disppearing messages legacy mode until after the platform agreed timestamp
if (Date.now() < disappearingMessagesV2ReleaseTimestamp) {

Loading…
Cancel
Save