Managing VBS Configuration Migrations from Non-Prod to Prod while in Different Versions

Summary:

We are preparing for a go-live for our client in early October on the 25C version. However, our non-production environment will be upgraded to 25D ahead of our production environment, which will remain on 25C for a while.

Given that source and destination environments must be on the same version for VBS configuration migrations, how to typically handle defect fixes or necessary migrations when non-prod and prod environments are on different release schedules?

We are looking for best practices or strategies to manage configuration changes under these staggered cadence scenarios.

Version (include the version you are using, if applicable):