Unstable versions 1.2.1 and 1.2.2 were deployed with PhET-iO releases

[jessegreenberg]

The last official maintenance release that I was aware of was 1.2.0, which was deployed with phetsims/tasks#818. PhET-iO releases on May 9 and May 16 also published versions 1.2.1 and 1.2.2, which are unstable and include accessibility features that we did not want deployed to production.

@zepumph @jbphet can you help determine what happened? Did this happen because there is both a 1.2 branch and a 1.2-phetio branch?

In the mean time, what is the best way to revert deployed version? Can I build 2.0 again off of 2.0 SHAS and deploy-production?

[jessegreenberg]

I talked with @jbphet, we think there are two possibilities for why this happened.

• The build tools deployed to production because there are both a 1.2 branch and a 1.2-phetio branch.
• In the deployment of 1.2.1 and 1.2.2 in the 1.2-phetio branch, the phetio brand flag might have been omitted.

Unsure of how the phetio build process works, but the second option seems likely. phetsims/tasks#848 is tracking a minor release for 1.3-phetio, so the first point should not happen in the next release.

To fix this, we will redeploy off of 1.2 SHAS, increment the version number to 1.2.3 as the latest version.

[jessegreenberg]

1.2.3 was deployed as a maintenance release to fix this. Thanks for the help @jbphet and @phet-steele. Closing.