Skip to content

fix: custom PHP binary package not pruned on build #204

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Apr 4, 2025

Conversation

SRWieZ
Copy link
Member

@SRWieZ SRWieZ commented Apr 4, 2025

This bug bundled every PHP version when custom PHP binaries were used, resulting in a large Electron file and blocking the notarization process.

  • Increased timeout for composer install
  • Clean up custom PHP binary package directory

@SRWieZ
Copy link
Member Author

SRWieZ commented Apr 4, 2025

Thanks to GitHub CI & PHPStan, I found an error I hadn't noticed :)

@SRWieZ
Copy link
Member Author

SRWieZ commented Apr 4, 2025

Oh wait I copy pasted the wrong version

@SRWieZ
Copy link
Member Author

SRWieZ commented Apr 4, 2025

Just a little failsafe

@PeteBishwhip PeteBishwhip merged commit 3cf8dca into main Apr 4, 2025
29 of 30 checks passed
@PeteBishwhip PeteBishwhip deleted the fix-custom-php-binary-not-pruned branch April 4, 2025 19:02
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.

3 participants