Closed tcpaddock closed 1 year ago
Hi @tcpaddock, this definitely should not happen.
Can you try to add the following to the GitHub Actions semantic-release config:
with:
...
custom-arguments: --provider-opt github_use_compare_commits=true
This will use the compare commits API from GitHub and should resolve your issue.
For more context: https://github.com/go-semantic-release/provider-github/issues/5
Hi, I'm having trouble producing consistent releases. I've tried merge PRs and squash PRs. In both cases, the GitHub action job logs the latest commit correctly but it fails to calculate a change. My current workaround is to delete the latest release and rerun job. This picks up the commits from the deleted release and the missing commits. At some point, this won't be an option.
For example, this run is expected to create release version 1.0.0-alpha.5.