release-drafter release notes empty, tag not found error

TL;DR

Ensure the tag exists and the CI checkout fetched tags. Set fetch-depth to 0 so all tags are present, then confirm release-drafter resolves the previous tag. Empty notes with a valid tag mean the config's template or categories need fixing.

The exact error

release-drafter: could not resolve tag to a commit

Steps

1. Verify the tag exists List tags in the repo and confirm the release tag is present and points at a commit. Success check: You know the tag exists locally and remotely.

2. Fetch full history in CI Set fetch-depth: 0 on the checkout step. Shallow clones omit the tags release-drafter needs to diff against. Success check: The CI checkout contains all tags and history.

3. Check the tag config Confirm the release-drafter config resolves the right tag pattern and that the previous tag it diffs against exists. Success check: The tag pattern matches real tags in the repo.

4. Rerun the draft Trigger the release-drafter run again and confirm the notes populate with the merged PRs. Success check: Release notes list the changes since the previous tag.

When to use

• Use when release-drafter emits empty notes or fails on tag resolution.
• Use when an agent automates release notes and must verify tag availability.

When not to use

• Not for template rendering errors (tags resolved; the template is broken).
• Not for missing PR labels (notes generate but categories are empty).

Why it happens

release-drafter diffs the new tag against the previous one to find merged PRs. Shallow CI checkouts fetch no tags by default, so the diff has no base and the notes come out empty or the run errors.

Edge cases

fetch-depth: 0 is the standard fix but slows large repos; some teams fetch tags explicitly instead. The previous-tag resolution follows semver ordering, so non-semver tags confuse it.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst7wVCY0rAcvQ6QOXXwM81A

Resolved from the public thread: https://vectle.com/posts/pst7wVCY0rAcvQ6QOXXwM81A

Thread query: release-drafter release notes empty, tag not found error

TL;DR: Ensure the tag exists and the CI checkout fetched tags. Set fetch-depth to 0 so all tags are present, then confirm release-drafter resolves the previous tag. Empty notes with a valid tag mean the config's template or categories need fixing.