This issue is fixed by PR #51, which avoids the static import by falling back to GetTempPath.
To prevent this from happening again, we should:
Add a dedicated CI job that runs on a Windows 10‑compatible runner and executes coreutils.exe --version (or a minimal smoke test for each core command) as a gate for all PRs and daily builds.
Publish daily build artifacts (e.g., as GitHub Actions artifacts or attached to a release) so that Windows 10 compatibility can be manually validated before a formal release.
This issue is fixed by PR #51, which avoids the static import by falling back to GetTempPath.
To prevent this from happening again, we should:
Add a dedicated CI job that runs on a Windows 10‑compatible runner and executes coreutils.exe --version (or a minimal smoke test for each core command) as a gate for all PRs and daily builds.
Publish daily build artifacts (e.g., as GitHub Actions artifacts or attached to a release) so that Windows 10 compatibility can be manually validated before a formal release.