Since the upgrade to Node 16, the CI workflow has been failing, and needed updating. Some upgrades were also needed since they required an old version of node-gyp, which caused yarn install to fail on the latest Windows runner.
Removed semantic-release and related packages. I can't find any evidence they are used anymore. Related to the node-gyp issue.
Moved vsce out of root and into the two workspaces it is used in. Also upgraded to @vscode/vsce.
Upgraded lerna. Our version was quite old, and relied on an old node-gyp.
Refactored CI workflow. Upgraded actions to latest versions, and uses built-in yarn caching. Also the ruby version matrix for testing the language server is no longer needed, as it uses the prebuilt, checked-in tree-sitter-ruby.wasm.
I believe the current failures in CI now are true failures. Some diagnosing on Windows is required.
Since the upgrade to Node 16, the CI workflow has been failing, and needed updating. Some upgrades were also needed since they required an old version of
node-gyp
, which causedyarn install
to fail on the latest Windows runner.semantic-release
and related packages. I can't find any evidence they are used anymore. Related to thenode-gyp
issue.vsce
out of root and into the two workspaces it is used in. Also upgraded to@vscode/vsce
.lerna
. Our version was quite old, and relied on an oldnode-gyp
.tree-sitter-ruby.wasm
.I believe the current failures in CI now are true failures. Some diagnosing on Windows is required.
You can see the latest run from my fork here: https://github.com/chasestubblefield/vscode-ruby/actions/runs/3671826946