PHAR.IO - How to make a PHAR release on GitHub PHIVE-compatible

How to make a PHAR release on GitHub
PHIVE-compatible

Prerequisites

You need a personal or company GPG key. If you don't have one, this explains how to generate a GPG key.
The public key of your GPG key needs to be known by the SKS keyservers. If you didn't upload it yet, this explains how to register it.
You already created a PHAR file.

Create a signature

gpg -u john@example.com --detach-sign --output {your_phar_name}.phar.asc {your_phar_name}.phar

About the options:

-u (optional) Provide a search term for the USER-ID you intend to use, if you have more than one.
--detach-sign Create a detached signature (do not wrap the original file).
--output Specify the filename of the signature (PHIVE currently searches for {your_phar_name}.phar.asc).

Last argument is the PHAR you want to sign.

Upload in GitHub's release section

Go to https://github.com/<your-vendor>/<your-project>/releases
Click "Edit" on your latest tag/release
Add {your_phar_name}.phar and {your_phar_name}.phar.asc in the "Attach binaries..." section
Click "Update release"