<#499 chore: fix issue with prebuildify> Pull requ...
# pact-js-development
g
#499 chore: fix issue with prebuildify Pull request opened by mefellows Prebuildify is for some reason looking for node 22 headers, this change: • sets node target based on current node version • update to prebuildify 6.0.1 to fix windows EINVAL issue pact-foundation/pact-js-core GitHub Actions: test (20, windows-latest) GitHub Actions: test (20, ubuntu-latest) GitHub Actions: test (20, macos-12) GitHub Actions: test (20, macos-14) GitHub Actions: test (18, windows-latest) GitHub Actions: test (18, ubuntu-latest) GitHub Actions: test (18, macos-12) GitHub Actions: test (18, macos-14) GitHub Actions: test (16, windows-latest) GitHub Actions: test (16, ubuntu-latest) GitHub Actions: release_dry_run GitHub Actions: test (16, macos-12) GitHub Actions: test (16, macos-14) GitHub Actions: test (20, windows-latest) GitHub Actions: test (20, ubuntu-latest) GitHub Actions: test (20, macos-12) GitHub Actions: test (20, macos-14) GitHub Actions: test (18, windows-latest) GitHub Actions: test (18, ubuntu-latest) GitHub Actions: test (18, macos-12) GitHub Actions: test (18, macos-14) GitHub Actions: test (16, windows-latest) GitHub Actions: release_dry_run GitHub Actions: test (16, ubuntu-latest) GitHub Actions: test (16, macos-12) GitHub Actions: test (16, macos-14) ✅ 4 other checks have passed 4/30 successful checks