Add PHAR file and a signature to Release Process

[szepeviktor]

From #122

Dear @TomasVotruba!

Please upload

1. a PHAR file
2. and its signature to releases as attachments

The singing key has to be published on keyservers once.

This way phive install migrify/migrify will simply work.

[szepeviktor]

I see! There is no box config to just generate PHAR files :(

[szepeviktor]

https://github.com/humbug/box generates PHAR files automatically.

e.g.

phive install --force-accept-unsigned humbug/box
tools/box compile --working-dir=packages/class-presence

[szepeviktor]

Should there be several PHAR-s? One for each package??

[TomasVotruba]

Should there be several PHAR-s? One for each package??

Yes, for each package you need this way 👍

migrify/migrify is a monorepo, like symfony/symfony, so you should never use it directly, just particular packages

[szepeviktor]

Would you like to upload release attachments (thus PHAR files + signatures) manually or in GitHub Actions?

[TomasVotruba]

That would be tedious with every tag. This process must be automated

[TomasVotruba]

Closing as accepted and only PR is needed. To keep more space for active issues, that need attention to resolve.

Thanks for understanding.

[szepeviktor]

Okay.

Here we make a GitHub Action phar-io/phive#278