As we all know, Premiere projects cannot cross major update lines, a standard project created in v23 cannot be opened in v24 without first creating a copy of the project compatable with v24. Typically, with offline projects, Premiere will warn the user when a project created with a previous version is opened with a new version so the user can decide whether to upgrade the project itself or revert to using the older app.
Unfortunately, Team Projects do NOT warn the user in a similar manner when a project that was created with a previous version of Premiere is opened with a new version. This can create issues if an editor unwittingly opens a team project using a new version of Premiere and shares their changes from the new version, effectively locking the team project into the new version and forcing all other team members to update to the new version prematurely. Upgrading Premiere to a new major version in the middle of an active project is definitely not what a team wants to do while still feeling confident that they won't encounter any unknown issues or bugs.
Normally, I'm happy accepting user error as the problem at hand, but the fact that Creative Cloud defaults to auto-updating apps really makes me wish that there would at least be a warning pop-up letting the user know about the potential issue the same way there is for non-team projects. (Either that or make auto-update NOT be the default behavior in Creative Cloud.)
AdChoices