"auth" schema differs between CLI setup and cloud, 'column "scopes" of relation "sessions" does not exist'

[stefan-girlich]

I'm frequently mirroring data from my prod environment (cloud) to my local environment (CLI, v2.65.5).
Today I noticed that my mirroring script (using supabase db dump and psql) failed with the following error when trying to ingest the prod data in my local database:

column "scopes" of relation "sessions" does not exist
 ...refresh_token_hmac_key", "refresh_token_counter", "scopes")

The "scopes" column is actually missing in my local auth.sessions table. My workaround is to manually add the missing column:

ALTER TABLE auth.sessions ADD COLUMN scopes TEXT NULL;

Another approach could be to exclude the table from the data dump via supabase db dump --exclude <table_name>.

Until now, the latest cloud and CLI schemas have always been in sync for me.
Would somebody know if this discrepancy is just a one-off or if I should prepare for more? Maybe somebody from the team can share what the policy is. I know that the auth schema is specifically protected, so maybe special rules apply concerning the tables.