8000 chore(db): drop the old getting started tables and column by kaposke · Pull Request #8168 · NangoHQ/nango · GitHub
[go: up one dir, main page]

Skip to content

chore(db): drop the old getting started tables and column - #8168

Open
kaposke wants to merge 1 commit into
gui/NAN-7976/chore-remove-old-getting-startedfrom
gui/NAN-7976/chore-drop-old-getting-started
Open

kaposke wants to merge 1 commit into
gui/NAN-7976/chore-remove-old-getting-startedfrom
gui/NAN-7976/chore-drop-old-getting-started

Conversation

@kaposke
@kaposke kaposke commented Nov 4, 2026 •
Copy link
Copy Markdown
Contributor

Part of NAN-7976. Drops the storage the old Getting started flow used. Nothing reads it since #8165.

  • Drops the getting_started_progress and getting_started_meta tables.
  • Drops _nango_users.getting_started_closed and its DBUser field.

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 down is empty.

@kaposke
kaposke added this pull request to stack #8147 November 4, 2026 15:33
@linear-code
linear-code Bot commented Nov 4, 2026
Copy link
Copy Markdown

NAN-7976

@cubic-dev-ai cubic-dev-ai Bot left a comment
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1 issue found across 2 files

Confidence score: 2/5

  • 20261104120000_drop_old_getting_started.cjs can 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

* @param {import('knex').Knex} knex
*/
exports.up = async function (knex) {
await knex.schema.dropTableIfExists('getting_started_progress');
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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>

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Won't merge with the stack. I've only put it on the stack for visibility

@kaposke
kaposke requested a review from a team November 4, 2026 15:37
@kaposke
kaposke marked this pull request as ready for review November 4, 2026 15:37
@kaposke
kaposke force-pushed the gui/NAN-7976/chore-drop-old-getting-started branch from 8162582 to 4e35759 Compare November 4, 2026 20:17
@kaposke
kaposke force-pushed the gui/NAN-7976/chore-drop-old-getting-started branch from 4e35759 to 7793454 Compare November 5, 2026 13:46
@kaposke
kaposke force-pushed the gui/NAN-7976/chore-drop-old-getting-started branch from 7793454 to cd0d266 Compare November 5, 2026 13:48
@kaposke
kaposke force-pushed the gui/NAN-7976/chore-drop-old-getting-started branch from cd0d266 to faaa73a Compare November 5, 2026 14:27
@kaposke
kaposke force-pushed the gui/NAN-7976/chore-drop-old-getting-started branch from faaa73a to 453446d Compare November 5, 2026 15:58

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

0