-
Notifications
You must be signed in to change notification settings - Fork 59
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
Sign PHAR #244
Comments
Possibly feasible once we move to github actions, and then we can use an organization secret where to store a GPG signing (sub-)key |
Thank you for considering this! |
The 5.0.0 release does not have a PHAR (yet). Will one be published? Thanks! |
Guess something broke (AGAIN) in the travis publishing logic. |
@sebastianbergmann for now, I attached a manually built phar to the release @ https://github.com/Roave/BackwardCompatibilityCheck/releases/tag/5.0.0 |
Because the PHP Archives (PHARs) of this tool are currently not signed, the
--force-accept-unsigned
option is required when using Phive to install/update this tool.Please consider signing the PHP Archives (PHARs) of this tool with a GPG key and publish that signature alongside the signed PHAR so that
--force-accept-unsigned
is not required when using Phive.Thank you!
The text was updated successfully, but these errors were encountered: