Description

The latest fpm release does not work with setup-fpm anymore.

I believe the reason is that the name of the assets was changed in #1044, where the artifact names were added the gcc-12 suffix. @gnikit any idea whether we should change this? maybe the safest way to handle it would be to have setup-fpm also check for said suffixes

Expected Behaviour

setup-fpm should definitely be updated to pick up this change. However, this naming change may be breaking other stuff.

Version of fpm

0.11.0

Platform and Architecture

all

Additional Information

No response