Wrong commit selection

[MaximeLaurenty]

Github Sentry Action Release Bug Report

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/[email protected]
  env:
    SENTRY_AUTH_TOKEN: ${{ secrets.SENTRY_AUTH_TOKEN }}
    SENTRY_ORG: ${{ secrets.SENTRY_ORG }}
  with:
    environment: prod
    projects: frontend
    sourcemaps: frontend
    version: ${{ 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 fe51918): see here the release just before (which includes fe51918): links to sentry if you have access: erroneous release, right release before that & list of our releases There is no relevant info in the logs of the action.

[mmospanenko]

maybe it requires more commits in current session?

      - uses: actions/checkout@v3
        with:
          fetch-depth: 0

[MaximeLaurenty]

How would adding more commits to the available history in github action lead to less commits on sentry releases? Fyi all our releases already have at least one commit. (and in our case: each release should have exactly one commit given we create a release and deploy after every commit)