Fixing Sentry release, “No commits found. Change commits range…”
When the getsentry/action-release GitHub action fails with “No commits found. Change commits range, initial depth or use — ignore-empty to allow empty patch sets.”
My GitHub deployment workflow, when attempting to upload source maps to Sentry, recently failed with the following unhelpful error.