Debating whether to sign the PHAR with a subkey, and upload the .asc to the releases as well. That way, people can install via Phive without requiring the --force-accept-unsigned flag.
With this workflow, PHAR files would be uploaded to GitHub Releases on tag, allowing for installs via Phive with:
Debating whether to sign the PHAR with a subkey, and upload the
.asc
to the releases as well. That way, people can install via Phive without requiring the--force-accept-unsigned
flag.With this workflow, PHAR files would be uploaded to GitHub Releases on tag, allowing for installs via Phive with: