Repository navigation
Conversation
Sorry, something went wrong.
There was a problem hiding this comment.
1 issue found across 2 files
Confidence score: 2/5
20261104120000_drop_old_getting_started.cjscan make pre-#8165 instances fail during rollout, and the migration cannot be reverted. Keep it out of the same stacked merge as #8165.
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="packages/database/lib/migrations/20261104120000_drop_old_getting_started.cjs">
<violation number="1" location="packages/database/lib/migrations/20261104120000_drop_old_getting_started.cjs:7">
P1: This migration runs on server boot and cannot be reverted, so it must not ship in the same stacked merge as #8165. The pre-#8165 instances still reading these tables will fail during rollout. Hold this PR out of the stack merge until #8165 is live in production.</violation>
</file>
Reply with feedback, questions, or to request a fix.
View guided diff | Re-trigger cubic
Sorry, something went wrong.
| * @param {import('knex').Knex} knex | ||
| */ | ||
| exports.up = async function (knex) { | ||
| await knex.schema.dropTableIfExists('getting_started_progress'); |
There was a problem hiding this comment.
P1: This migration runs on server boot and cannot be reverted, so it must not ship in the same stacked merge as #8165. The pre-#8165 instances still reading these tables will fail during rollout. Hold this PR out of the stack merge until #8165 is live in production.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At packages/database/lib/migrations/20261104120000_drop_old_getting_started.cjs, line 7:
<comment>This migration runs on server boot and cannot be reverted, so it must not ship in the same stacked merge as #8165. The pre-#8165 instances still reading these tables will fail during rollout. Hold this PR out of the stack merge until #8165 is live in production.</comment>
<file context>
@@ -0,0 +1,17 @@
+ * @param {import('knex').Knex} knex
+ */
+exports.up = async function (knex) {
+ await knex.schema.dropTableIfExists('getting_started_progress');
+ await knex.schema.dropTableIfExists('getting_started_meta');
+
</file context>
Sorry, something went wrong.
There was a problem hiding this comment.
Won't merge with the stack. I've only put it on the stack for visibility
Sorry, something went wrong.
8162582 to
4e35759
Compare
4e35759 to
7793454
Compare
7793454 to
cd0d266
Compare
cd0d266 to
faaa73a
Compare
faaa73a to
453446d
Compare
Part of NAN-7976. Drops the storage the old Getting started flow used. Nothing reads it since #8165.
getting_started_progressandgetting_started_metatables._nango_users.getting_started_closedand itsDBUserfield.Merge only once #8165 is deployed. The server that's live before it still reads and writes these, so dropping them earlier breaks it during the rollout. This can't be undone: the data is gone and the
downis empty.