[4.x] Is the plugins table schemaVersion meant to be updated to reflect the project YAML?

[jlawrence-yellostudio]

Hi @brandonkelly

I have been fighting with a bit of an issue recently. A colleague of mine made the mistake on a project of incrementing schemaVersion on two of their plugins, even though there was no change to the schemaVersion, and then when the error was pointed out, they reverted it back to 1.0.0. However it appears regardless of what I do i cant get this to automatically revert back to 1.0.0 via YAML without manually editing the plugins table.

I have confirmed that the root project.yaml contains 1.0.0 for the schemaVersion for both plugins and the plugins do not specify a schemaVersion (therefore would be 1.0.0 by default) however it appears that even with force applying the YAML, the schemaVersion column does not get updated. The issue is that for some reason if i do a rebuild of the YAML it appears to take the schemaVersion from the plugins table and we end up stuck back in that cycle.

Do you have any recommendations for what I can do to resolve this? or is the only solution to manually edit the values in the plugins table?

Craft CMS 4.16.14
Many thanks!

[brandonkelly]

A colleague of mine made the mistake on a project of incrementing schemaVersion on two of their plugins, even though there was no change to the schemaVersion

What do you mean by that? By incrementing the schemaVersion, there… was a change to the schemaVersion.

[jlawrence-yellostudio]

Hi @brandonkelly
Apologies, for the lack of clarity with that statement. I meant that he thought he had to increment both values. His plugins don't have any database tables. When he was informed that schemaVersion was meant to respresent schema changes, he reverted back to using 1.0.0 for the value. But no matter what i try these values seem to keep coming back when i deploy to a database I haven't manually edited to fix it. I was wondering if the YAML value is ignored for this and if the plugin table value takes priority over it?

[brandonkelly]

If the schema version bump already made its way out to the public, then your best bet would be to just revert back to the increased value. (There’s no harm in bumping the schema version; just a little awkward if it was unnecessary as it will cause Craft to require that the plugin’s new migrations be run, of which there are zero.)

If it’s only used internally then you can fix by changing the schemaVersion value in the plugins database table, as well as run the following command:

php craft pc/set plugins.myPluginHandle.schemaVersion 1.0.0 && \
php craft pc/touch