Joram van den Boezem

Since I use `yarn` for all my (mono)repos, I created [semantic-release-yarn](https://github.com/hongaar/semantic-release-yarn) which supports monorepos natively

That is a link to my unofficial successor since this project seems abandoned.

Is anyone working on this issue already, or anyone who would have some pointers? I would love to look into this as a solution to this bug would mean a...

@MoLow thanks for the review ~I can't find any reference for the fn return type signature of `TestFn` though?~ Edit: misinterpreted your suggestion 🤦 will apply your changes! Edit2: couldn't...

In order to test these changes, I wrote a quick `tsd` test in `test/test.test-d.ts`: ```ts import { expectType } from "tsd"; import test, { describe, it } from "../lib/test.js"; //...

I have the same problem here, the server generates invalid JSON as not all the backslashes in the file paths are escaped. This is the output generated for my project...

Hi @bradjones1, thanks for reporting this. I have no time currently to look at this but I'll leave the issue open. Feel free to contribute a PR, I'd be happy...

It's not very clear from the yarn docs, but one of the advantages of using `yarn version` is that it updates `workspace:` references in monorepos. See https://yarnpkg.com/cli/version/apply for more information....

Can you try setting the GIT_STRATEGY to `clone`: ```yaml variables: GIT_STRATEGY: clone ``` See also https://docs.gitlab.com/ee/ci/runners/configure_runners.html#git-strategy