-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automated maintenance release: interactive-description file rename #48
Comments
Here is the commit that renamed the file in phetmarks.js: b63edcd |
I expected recent branches like ratio-and-proportion to not need this, but I manually checked and indeed it does. energy-skate-park-basics 1.4 is quite old so I want to understand why the process skipped this one. EDIT: It is because the most recent release branch of ESP:B is 1.1. 1.4 is unpublished AND for some reason does not have phetmarks in its dependencies.json. But 1.1 DOES have phetmarks in its dependencies, and the process did add a needed patch for energy-skate-park-basics 1.1. |
I need to find the commit that added EDIT:
EDIT2: After iterating over creating and applying patches to the above list, I determined a few more did not need this change because their phetmarks SHA did not include
|
Hit a build error while running Maintenance.updateDependencies:
|
On a different machine (without local commits for this issue) when I checkout capacitor-lab-basics 1.7 branch and dependencies.json SHAs (with npm update in sim and chipper) and run @samreid or @zepumph would you mind taking a look or recommending how to proceed? I am going to temporarily remove capacitor-lab-basics 1.7 from maintenance.json and continue with Maintenance.updateDependencies() for now. EDIT: Removed capacitor-lab-basics 1.7 entry for safe keeping:
|
I'll take a look. |
The most recent CLB version published for PhET-iO is 1.6. How was phet-io brand added to 1.7 as a supported brand by the MR process? I look at the phet-io deploy status as well as the master phet-io spreadsheet and neither have 1.7 on it? I see 1.7 is not currently published for either brand (last RC was phetsims/qa#588), but dev test on the way? (phetsims/qa#616). Over to JO with two questions:
|
That is correct, these are not being republished. Sorry, do what for each phet-io brand? |
If the entries you are removing are specific to phet-io brand, but in a branch that is getting a phet brand MR also, then can't we just remove them anyways and the phet MR |
Ah, yes - that could work. The only exception so far is molarity 1.4 which only has phet-io brand (entry in #48 (comment)). phet brand is published at 1.5. |
So what I would do is add the removed entries back into maintenance.json, but remove the "phet-io" from the brands array in #48 (comment) (for example). |
OK, updatedDependencies is complete. Sims that failed were |
I tried #48 (comment) but I am not able to run updateDependencies for the sims that failed. All I get is
Against the same entry after the failure:
EDIT: Keeping track of the same data for molarity 1.4 and capacitor-lab-basics 1.7 so I can try those again too:
capacitor-lab-basics 1.7:
|
Removing brand
@zepumph do you have any thoughts about 1 above and do the others seem reasonable? |
Yes that is excellent. Please assign me on all of them. but (2) (JO) |
OK sounds great! Issues have been opened. Leaving you assigned here for the last part.
|
molarity 1.4 has been patched. Anything else here? |
Thats it, thanks @zepumph - closing. |
Perennial had a file called "interactive-descriptions" that was renamed to "interactive-description" for consistency. However, since phetmarks is versioned and perennial isn't this means that phetmarks is broken for sims with a phetmarks SHA prior to the rename.
In phetsims/a11y-research#157 (comment) and phetsims/a11y-research#157 (comment) we decided to use the automated maintenance release process to apply the rename commits to release branches so phetmarks works. We agreed that applying patches is sufficient for this and we don't need to actually republish sims. So I will go through the
updateDependencies()
step of the MR process and then stop there.MR commits will be made against this issue, and I will document patch SHAs here.
The text was updated successfully, but these errors were encountered: