Unable to Publish any VB Changes During SOAK Because of Version Mismatch Works Only After Go‑Live

We’re running into a recurring issue with VB Studio during our SOAK period, and I’m hoping others have seen this or have guidance. During SOAK testing deploying/publishing from VB Studio fails completely. Even though we are publishing and deploying from the main branch which is unrelated to our dedicated release branch it causes it to fail due to version differences. This effectively means we cannot publish any changes for the entire 6‑week SOAK window within our TEST environment to PROD, which isn’t realistic for our team. How do other teams handle SOAK when VB Changes outside newest release? We