Summary
At the end of the new arch project setup, if dependencies were changed (as happens when adding the example in cpp-lib) we try to run yarn install. This fails in CI for the cpp-lib template added in #12481, probably having to do with the newer version of yarn used by that template.
Motivation
The template setup already fails gracefully if the install ever fails, telling the user to run the install manually instead. The upstream library template also asks the user to run the install manually, so it's not without precedent. But this is only failing in CI, locally the command seems to work find. So while the failing gracefully okay and a good insulation against other unrelated issues that may block the install, we should be able to figure out why the install works locally and make it work in CI too.
Basic Example
No response
Open Questions
No response
Summary
At the end of the new arch project setup, if dependencies were changed (as happens when adding the example in
cpp-lib) we try to runyarn install. This fails in CI for thecpp-libtemplate added in #12481, probably having to do with the newer version of yarn used by that template.Motivation
The template setup already fails gracefully if the install ever fails, telling the user to run the install manually instead. The upstream library template also asks the user to run the install manually, so it's not without precedent. But this is only failing in CI, locally the command seems to work find. So while the failing gracefully okay and a good insulation against other unrelated issues that may block the install, we should be able to figure out why the install works locally and make it work in CI too.
Basic Example
No response
Open Questions
No response