Skip to content

fix: add win32-x64 to PHAR_FALLBACK_PKGS alongside win32-arm64#150

Merged
jasdeepkhalsa merged 1 commit intomasterfrom
feature/win-fix-release-5
Mar 7, 2026
Merged

fix: add win32-x64 to PHAR_FALLBACK_PKGS alongside win32-arm64#150
jasdeepkhalsa merged 1 commit intomasterfrom
feature/win-fix-release-5

Conversation

@jasdeepkhalsa
Copy link
Copy Markdown
Member

@dbdiff/cli-win32-x64 was being published as an empty skeleton accidentally (the npm check saw 'already on registry' from a prior run). Since the SPC zlib linker bug means win32-x64 also has no native binary, make it explicitly intentional by adding it to PHAR_FALLBACK_PKGS.

Both Windows packages are now published as documented PHAR-fallback skeletons: bin/dbdiff.js falls back to 'php dbdiff.phar' for both.

@dbdiff/cli-win32-x64 was being published as an empty skeleton
accidentally (the npm check saw 'already on registry' from a prior run).
Since the SPC zlib linker bug means win32-x64 also has no native binary,
make it explicitly intentional by adding it to PHAR_FALLBACK_PKGS.

Both Windows packages are now published as documented PHAR-fallback
skeletons: bin/dbdiff.js falls back to 'php dbdiff.phar' for both.
@jasdeepkhalsa jasdeepkhalsa merged commit 4e33fba into master Mar 7, 2026
56 checks passed
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud bot commented Mar 7, 2026

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant