ci: release assets for macos x64 and arm64 (M1)

[CyberHippo]

Description

• Fixes the release of macos package assets

The release workflow did not find any macos assets to upload:

🤔 Pattern 'dist/macos/asyncapi.pkg' does not match any files.
🤔 dist/macos/asyncapi.pkg not include valid file.

This was caused by oclif which is now supporting arm64 arch (See oclif/oclif#847). The macos assets are now ${name}-v${version}-${sha}-x64.pkg and ${name}-v${version}-${sha}-arm64.pkg:

Run ls -la dist/macos/
total 581912
drwxr-xr-x  4 runner  staff        128 Apr 13 11:33 .
drwxr-xr-x  4 runner  staff        128 Apr 13 11:33 ..
-rw-r--r--  1 runner  staff  148119971 Apr 13 11:33 asyncapi-v0.37.2-82ba8ff-arm64.pkg
-rw-r--r--  1 runner  staff  149812837 Apr 13 11:33 asyncapi-v0.37.2-82ba8ff-x64.pkg

@derberg We could use the glob pattern matching for the files of the Action softprops/action-gh-release@v1 instead of passing the full file name. What do you think ?

      - name: Update release
        uses: softprops/action-gh-release@v1
        with:
          files: dist/${{ matrix.dist_folder }}/*
          tag_name: v${{ steps.extractver.outputs.version }}
          token: ${{ secrets.GH_TOKEN }}

Related issue(s)
See also #501.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[derberg]

@CyberHippo

@derberg We could use the glob pattern matching for the files of the Action softprops/action-gh-release@v1 instead of passing the full file name. What do you think ?

can you open a separate issue for that topic. I think we in general need to come up with an idea on how to make sure we know earlier that these distros are failing on a release

[derberg]

THANKS!!!

[derberg]

/rtm

[asyncapi-bot]

🎉 This PR is included in version 0.38.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀