@johnnyreilly is this the right branch for any version 8 patches?

It is yes - I've never tried publishing from a branch that isn't main using the GitHub Actions workflow. Wonder if it works....

Failing comparison tests - you may want to regenerate the output for the failing tests. See https://github.com/TypeStrong/ts-loader/tree/main/test/comparison-tests#regenerating-test-data

I think you may have regenerated all of the test output, rather than just the failing test cases?

I regenerated the tests, but I don't think they'll succeed on the server check happening now. There are trivial differences and root path differences.

And I'm not expecting so many differences anyway.

Yeah - I think there's something wrong with your backport

@johnnyreilly gonna need some help please. I don't know what I'm looking at.

So to regenerate the failing test I did this: yarn run comparison-tests -- --save-output --single-test projectReferencesSymLinks

Yes, I ran exactly that (although I also ran "instance" since that one was also listed as failing, from my reading).

I did it in the context of ts-loaders devcontainer (but that shouldn't matter). Looks like bad things are happening in GitHub Actions at the moment; seeing random failures

yarn run comparison-tests -- --single-test projectReferencesSymLinks_WatchApi --save-output

good, right?

Yup - good. This is where we find out if the automation works for the non-main branch...

https://github.com/TypeStrong/ts-loader/actions/runs/778506165

https://www.npmjs.com/package/ts-loader/v/8.2.0