Skip to content

Conversation

@AndrewKostka
Copy link
Contributor

Bug: T412133

@tarrow
Copy link
Contributor

tarrow commented Dec 17, 2025

Why don't we want to update the schema name to 2? Isn't that exactly the point of versioning them so that we know which one was created from which source?

@tarrow
Copy link
Contributor

tarrow commented Jan 9, 2026

@dati18 asked me on mattermost what exactly I was looking for here; I was thinking that the neatest thing to do would be to revert the "avoid new version" commit. Merge this and then also follow up with the necessary changes to use the new schema which probably means making changes in:

and then changing the env variable WBSTACK_WIKI_DB_PROVISION_VERSION in staging and production. Right now they appear to be unset and so default to what is specified in:

'wiki_db_provision_version' => env('WBSTACK_WIKI_DB_PROVISION_VERSION', 'mw1.43-wbs1'),

I would recommend not changing this default immediately

Copy link
Contributor

@tarrow tarrow left a comment

Choose a reason for hiding this comment

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

sorry, I missed the revert already made it in

@dati18 dati18 merged commit 7c263c6 into main Jan 9, 2026
5 checks passed
@dati18 dati18 deleted the mw143-fix-missing-updatelog branch January 9, 2026 11:44
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.

4 participants