How to Manage Pipeline Deployment with Patch Level Mismatches in Oracle Environments?

Summary:
We are utilizing Oracle Visual Builder Studio to make updates to our Redwood pages. A recurring challenge we’ve encountered is the inability to deploy pipelines from Non-Prod to Production when the patch levels between environments differ (e.g., Non-Prod on 24D vs. Production on 24C).

While this behavior aligns with the expectation of consistent environments, it presents operational challenges, especially during the A6 cohort release cycle, where release testing can create a mismatch between Production and TEST environments for up to six weeks. This mismatch also impacts our ability to develop, test, and deploy fixes or enhancements during the window of patch level disparity.