* retry failed tests to see if we can avoid some of these flakes
* add longer timeouts to virtest isolation tests
* fix errors in test-and-check.yml
* reorganize test runs
* move GITHUB_TOKEN to pass-through env for turbo
* add logging to changeset-version tool
Previously the changeset-version.js script was failing in CI because we
were using `pnpm i`, which (in CI) defaults to a frozen lockfile.
This then failed, since we were actually trying to update the lockfile
with this command.
Now we explicitly tell pnpm to only update the lockfile and not worry about
actually installing anything.
* fix: ensure `Updated dependencies` version correct in `CHANGELOG.md`s
In the `changeset-version.js` script, we were replacing version
headers in `CHANGELOG.md` but not `Updated dependencies`, meaning
there were some dangling references to non-existent `miniflare`
versions.
* fixup! fix: ensure `Updated dependencies` version correct in `CHANGELOG.md`s
This workflow was failing whenever there was a minor release to wrangler
and a patch release to a package that depended upon wrangler.
It was caused by a bug in npm that was resolved in v8.5.0.
See https://github.com/npm/cli/issues/4379 and https://github.com/npm/cli/pull/4371.
The error looks like: `No matching version found for wrangler@^2.15.0.`
#2489 broke the `Release` CI with an error that `patch-package`
couldn't be found when running `changeset-version.js`.
It looks like the `npm install` script in `changeset-version.js` is
only installing production dependencies. Moving `patch-package` to
`dependencies` leads to another error that `ink` cannot be found to
apply the patch to.
However, the only reason we run `npm install` here is to update
`package-lock.json`, so we don't need to be running `postinstall`
scripts. Therefore, this PR adds the `--package-lock-only` flag.
See https://docs.npmjs.com/cli/v9/commands/npm-install.