Multiple environments in same VB Workspace

Summary:

Would like to understand what the correct behavior is when using multiple env in same VB workspace, same project.

We have lets say, below Envs:

Dev1 - upgraded to 25C - Used for VB

DEV3 - on 25B

Prod - on 25B

We are using dev1 for development and migration to prod, but due to being on different release there is a huge change that the deployment will fail. To overcome this, we try to utilize the dev3 env, create the package again and migrate to prod. Is this the best way to handle the migration? If not, how to ensure the deployment from