You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On e5d3297, both our package.json define scripts with a characted ':' in their name.
This is no problem in old versions of yarn but in newer versions scripts named like this are global scripts which is probably not what we intended here.
Out git runner is ubuntu-latest which has yarn 1.22.21 but as ubuntu-latest is a floating version, this can change at any time.
I'm not entirely sure if this is really the version of yarn used in our CI. It's possible but undocumented if setup-node@v4 installs and uses another yarn when node-version is set to 18.x
To prioritize this issue, we need to learn more about how global scripts are interpreted in newer versions.
The text was updated successfully, but these errors were encountered:
On e5d3297, both our package.json define scripts with a characted ':' in their name.
This is no problem in old versions of yarn but in newer versions scripts named like this are global scripts which is probably not what we intended here.
Out git runner is ubuntu-latest which has yarn 1.22.21 but as ubuntu-latest is a floating version, this can change at any time.
I'm not entirely sure if this is really the version of yarn used in our CI. It's possible but undocumented if setup-node@v4 installs and uses another yarn when node-version is set to 18.x
To prioritize this issue, we need to learn more about how global scripts are interpreted in newer versions.
The text was updated successfully, but these errors were encountered: