From e890f6bae4cd07a5e9a0a37aa800ce25fef2087c Mon Sep 17 00:00:00 2001 From: Alan Guo Xiang Tan Date: Tue, 27 Jan 2026 14:13:55 +0800 Subject: [PATCH] DEV: Add `upcoming_change_events` to excluded tables in migrations (#37319) What is the problem? The `migrations/bin/cli schema generate --db=intermediate_db` command fails with the error "Tables not configured or excluded: upcoming_change_events". The `upcoming_change_events` table was added in commit 8124ecab97 but was not added to the migrations schema configuration. What is the solution? Add `upcoming_change_events` to the `global.tables.exclude` list in `migrations/config/intermediate_db.yml`. This table is an internal system table for tracking admin feature notifications and is not relevant for data migrations between Discourse instances. --- migrations/config/intermediate_db.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/migrations/config/intermediate_db.yml b/migrations/config/intermediate_db.yml index 921707d4f02..db3b196da81 100644 --- a/migrations/config/intermediate_db.yml +++ b/migrations/config/intermediate_db.yml @@ -524,6 +524,7 @@ schema: - "topic_voting_votes" - "translation_overrides" - "unsubscribe_keys" + - "upcoming_change_events" - "upload_references" - "uploads" - "user_actions"