Label internal Windows hack thread

[jasagredo]

This thread is inaccessible from outside.

Before submitting your PR, check that you've:

• Bumped the version number

After submitting your PR:

• Update the Changelog.md file with a link to your PR
• Check that CI passes (or if it fails, for reasons unrelated to your change, like CI timeouts)

[jasagredo]

Should I bump the version number or add a changelog entry for this?

[Vlix]

This thread is inaccessible from outside.

What do you mean with this?
This PR is only for labeling the hacky thread?

[jasagredo]

I mean it is not possible for a user to label this thread. And yes, the PR is only for labeling the thread.

[Vlix]

Keeping the labeling outside the fork is less code and saves a few cycles, maybe 🙃

I've zero objections to this PR though, in general.

[Vlix]

Nightly Windows job fails with:
doctest > C:/Users/runneradmin/AppData/Local/Programs/stack/x86_64-windows/ghc-9.10.1/mingw/bin/strip.exe: error: Permission denied

I've heard about this before, doesn't block this PR.

@jasagredo How quickly do you need a release for this?
Please either bump the lower version and add an entry in the ChangeLog for that new version, or just add to the Changelog with an "Unreleased:" title.

[jasagredo]

Will add an Unreleased point in the changelog, thanks.

From my side there is no rush on getting this released. Whenever a new version is released is fine.

[kazu-yamamoto]

Nice catch!
Labeling threads is very good to me.
Thanks.