Closed markgammon closed 1 year ago
Since the BLL RC turned out awkward, I'll paste the steps for the CCK RC here (in case something goes wrong). I confirmed we are publishing 1.3. Then I pulled all repos and made sure I was in master for all repos. Then I started VPN and ran grunt rc --brands=phet,phet-io --branch=1.3
. I spot checked 2 dependency SHAs and they looked accurate. I tested PhET brand and Studio, and it worked well. Studio alt keys with stationary mouse are working great in the local test: https://github.com/phetsims/studio/issues/295
UPDATE: RC Publication complete, in https://github.com/phetsims/qa/issues/908
Issues from RC.1 addressed. Here is our list for cherry-picking:
https://github.com/phetsims/phet-io-sim-specific/commit/efbfbea32113677dfc6a28ee67d0134ed030fd3e
https://github.com/phetsims/phet-io-sim-specific/commit/264769f4b1454bc875b4f994e1a358796ac78b21
https://github.com/phetsims/circuit-construction-kit-common/commit/b11aeb34eeec7cf56a714474eb6d261ff6a41fee
https://github.com/phetsims/circuit-construction-kit-common/commit/1a255a938a5ddfff94c736c1de3f3e786acd7197
https://github.com/phetsims/circuit-construction-kit-common/commit/477fa0f2b76cd2b171eddafb414c2f590b8f7019
https://github.com/phetsims/circuit-construction-kit-common/commit/fd8bc3d23c1be0ca6b662d0b6e4848eea09bba72
https://github.com/phetsims/phet-io-sim-specific/commit/803edb64c72b0f33db4b21cd9befff85309324ae
https://github.com/phetsims/circuit-construction-kit-dc/commit/2cb906f5866f7a1d8d54cd85f42bf00c279c1232
https://github.com/phetsims/phet-io-sim-specific/commit/b69d67c577369748769d47968d2095e0edd19c3e
https://github.com/phetsims/phet-io-sim-specific/commit/67fb67f44e3affd9c9ab11cad8008e71daf1eff6
https://github.com/phetsims/circuit-construction-kit-common/commit/3ad9f7682d164a819dc85f996a86f2614ec216bd
https://github.com/phetsims/circuit-construction-kit-common/commit/1aa39b4946412e0332f9dfbc3294c06de4bb626d
https://github.com/phetsims/circuit-construction-kit-common/commit/a7de391c42e5081e56ab5aa7fbe4a6bc1ad3aac2
https://github.com/phetsims/phet-io-sim-specific/commit/b11125e9d79aeb64bfab5c1eaa8c43ff661c6390
https://github.com/phetsims/phet-io-sim-specific/commit/768b10ee914c1c4ecc323e1258fcd58fefa3fe76
STUDIO AUTOSELECT HOPEFULLY IN RC. Just test it.
Sorted:
NEWEST
https://github.com/phetsims/circuit-construction-kit-common/commit/a7de391c42e5081e56ab5aa7fbe4a6bc1ad3aac2
https://github.com/phetsims/circuit-construction-kit-common/commit/477fa0f2b76cd2b171eddafb414c2f590b8f7019
https://github.com/phetsims/circuit-construction-kit-common/commit/1aa39b4946412e0332f9dfbc3294c06de4bb626d
https://github.com/phetsims/circuit-construction-kit-common/commit/3ad9f7682d164a819dc85f996a86f2614ec216bd
https://github.com/phetsims/circuit-construction-kit-common/commit/1a255a938a5ddfff94c736c1de3f3e786acd7197
https://github.com/phetsims/circuit-construction-kit-common/commit/b11aeb34eeec7cf56a714474eb6d261ff6a41fee
https://github.com/phetsims/circuit-construction-kit-common/commit/fd8bc3d23c1be0ca6b662d0b6e4848eea09bba72
OLDEST
NEWEST
https://github.com/phetsims/phet-io-sim-specific/commit/768b10ee914c1c4ecc323e1258fcd58fefa3fe76
https://github.com/phetsims/phet-io-sim-specific/commit/b11125e9d79aeb64bfab5c1eaa8c43ff661c6390
https://github.com/phetsims/phet-io-sim-specific/commit/b69d67c577369748769d47968d2095e0edd19c3e
https://github.com/phetsims/phet-io-sim-specific/commit/264769f4b1454bc875b4f994e1a358796ac78b21
https://github.com/phetsims/phet-io-sim-specific/commit/efbfbea32113677dfc6a28ee67d0134ed030fd3e
https://github.com/phetsims/phet-io-sim-specific/commit/67fb67f44e3affd9c9ab11cad8008e71daf1eff6
https://github.com/phetsims/phet-io-sim-specific/commit/803edb64c72b0f33db4b21cd9befff85309324ae
OLDEST
https://github.com/phetsims/circuit-construction-kit-dc/commit/2cb906f5866f7a1d8d54cd85f42bf00c279c1232
One merge conflict, in ValueNode (related to Text.string/Text.txt change).
RC.3 published and up for testing.
RC.5 was verified, so I published it. It said:
PhET-iO deploys involve a couple of extra steps after production. Please ensure the following are accomplished:
I already did the above check box. Great work all!! Amazing to have this out!
Make sure the sim is listed in perennial/data/phet-io-api-stable if it has had a designed production release, and update the checked in API file to match the published version.
Yes, it is listed in phet-io-api stable.
update the checked in API file to match the published version.
This will cause API incompatibilities. I tested this by copying https://phet-io.colorado.edu/sims/circuit-construction-kit-dc/1.3/circuit-construction-kit-dc-phet-io-api.json into master and seeing numerous differences. @zepumph should we change the documentation about this process?
Ahh right. Yes, I think in general the instructions make sense, basically it is saying "we just published this API, let's see how different it is from master." In this case, we had a large reckoning in general
while this was in RC (in https://github.com/phetsims/phet-io/issues/1913), and decided it wasn't worth maintenance releasing to CCK and Molecule Shapes.
So all you have to do is make sure that the API is correct with master. Feel free to update the doc if it seems confusing.
I updated the docs, @zepumph sound good?
UPDATE: Specifically, I removed that phrase because we have other tooling to guarantee that the API file matches master.
Publish with the latest PhET-iO Studio code base and upgrades.
See milestone for remaining issues https://github.com/phetsims/circuit-construction-kit-common/milestone/5