[release] Work around the removal of yarn --silent

[douglowder]

Why

When yarn moved to version 4, they removed the --silent flag. Because of this change, any use of yarn to call scripts and get output will also get yarn debugging garbage, and there is no way to suppress it.

The release scripts are mostly ok with this, except for calling the next-version script. The output of this script has to be clean for it to be used as input for lerna version.

How

Replaced the yarn call with a direct invocation of the node Typescript source, bypassing yarn.

Test Plan

Since the trigger-release.yml workflow supports a dry run mode, it's safe to modify it to check out a test branch and run the workflow many times to debug the issue.

Once this change is merged, a dry run invocation of the workflow should succeed even if no version string is passed in.

[douglowder]

• [release] Work around the removal of yarn --silent #3424 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[github-actions]

⏩ The changelog entry check has been skipped since the "no changelog" label is present.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 52.32%. Comparing base (3e13df4) to head (fc905a2).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3424      +/-   ##
==========================================
- Coverage   52.60%   52.32%   -0.27%     
==========================================
  Files         806      807       +1     
  Lines       33604    33868     +264     
  Branches     6985     7033      +48     
==========================================
+ Hits        17673    17719      +46     
- Misses      14548    14750     +202     
- Partials     1383     1399      +16     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[douglowder]

Merge activity

• Feb 24, 11:37 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Feb 24, 11:37 AM UTC: @douglowder merged this pull request with Graphite.