Github Sentry Action Release Bug Report

This is a followup of #139 given @andreiborza's last comment and given the issue persists.

Environment

How do you use this action?
Standard Github runners, container built on top of archlinux:base

Which version of the action?
getsentry/[email protected]

Steps to Reproduce

1. Setup action in our CI, triggered on every commit to master

      - name: Create Sentry release
        uses: getsentry/action-release@fa247637f74d407f51d8423a5dc10abae1917873 # v3.1.0 # https://github.com/getsentry/action-release/tags
        env:
          SENTRY_AUTH_TOKEN: ${{ secrets.SENTRY_AUTH_TOKEN }}
          SENTRY_ORG: ${{ vars.SENTRY_ORG }}
        with:
          environment: prod
          projects: js-angular spindjango php-symfony
          sourcemaps: web
          release: ${{ github.sha }}
          dist: ${{ github.sha }}
          url_prefix: "~"

2. Make multiples commits to master
3. Check info about releases into Sentry

Expected Result

Have only 1 commit in every release.

Actual Result

Most of the time, commits are properly set within releases (just 1), but sometimes a discrepancy happens and a release contains multiple commits (for which releases already exist):
see here commits in the latest release (including previous bd4b346):

see here the release just before (which includes bd4b346 and only it):

links to sentry if you have access: erroneous release, right release before that & list of our releases
logs with actions debugging enabled (after obfuscation of RUNS_ON related information + removed most of the frontend files):
GHA_logs_sentry.txt