automatic phar creation for releases

[maglnet]

No description provided.

[maglnet]

Does anyone know a good way to check github actions locally?

[DanielBadura]

I saw this in my feed once: https://github.com/nektos/act
Never used it tho.

[Ocramius]

Yeah, act is the way :)

[maglnet]

Thanks for your input @DanielBadura @Ocramius

I'll try act next time instead of pushing over and over again :-)
Do you know if it's possible to test "releasing" and uploading?

If you don't see any further issues, I'll give this a first try for the next release and you may merge it @Ocramius ?

[Ocramius]

Do you know if it's possible to test "releasing" and uploading?

Not sure: it is potentially feasible to trigger act with a custom-crafted github event, but I'm no expert there.

I'll give this a first try for the next release and you may merge it @Ocramius ?

If you want, we can merge and trigger a release right now: wouldn't hurt.

[DanielBadura]

You could even release a beta release like 3.5.0-beta, no? So everyone knows something is getting tested in the release.

[maglnet]

I'm fine with both, beta and stable.
Let's go :-)

[Ocramius]

You could even release a beta release like 3.5.0-beta, no?

Not supported by release automation: 3.5.0 it is, and if it's borked, it will be 3.5.1 :-)

[Ocramius]

Indeed, it failed :D

https://github.com/maglnet/ComposerRequireChecker/runs/4164758607?check_suite_focus=true

Please do make a new PR for 3.5.x and we'll get it fixed in 3.5.1

[maglnet]

Ahh, lol :-)

I need to run composer install first, otherwise there's no phing available now to execute the composer install :-)