TagBot: Manual intervention needed for releases

[github-actions]

TagBot could not automatically create releases for the following versions. This may be because:

• The commits modify workflow files (.github/workflows/), which GITHUB_TOKEN cannot operate on
• The tag already exists but the release failed to be created
• A network or API error occurred

Versions needing manual release

• v0.3.5 at commit 6956b64b
  • Error: Git command 'git -C /tmp/tagbot_repo_oia71hgr push origin v0.3.5' failed
• v0.3.7 at commit 037240b9
  • Error: Git command 'git -C /tmp/tagbot_repo_oia71hgr push origin v0.3.7' failed
• v0.3.8 at commit e965e030
  • Error: Git command 'git -C /tmp/tagbot_repo_oia71hgr push origin v0.3.8' failed
• v0.3.9 at commit 292a753c
  • Error: Git command 'git -C /tmp/tagbot_repo_oia71hgr push origin v0.3.9' failed
• v1.2.0 at commit a359f38f
  • Error: Git command 'git -C /tmp/tagbot_repo_oia71hgr push origin v1.2.0' failed

How to fix

Run these commands locally:

git tag -a v0.3.5 6956b64b0ccb503fbe08fce87f8940e7ae9d31fe -m 'v0.3.5' && git push origin v0.3.5 && gh release create v0.3.5 --generate-notes
git tag -a v0.3.7 037240b9c06d528b49fe63289095ae0dd5162ebc -m 'v0.3.7' && git push origin v0.3.7 && gh release create v0.3.7 --generate-notes
git tag -a v0.3.8 e965e0302438bf1c21c285885bb0744ff480503b -m 'v0.3.8' && git push origin v0.3.8 && gh release create v0.3.8 --generate-notes
git tag -a v0.3.9 292a753cf55f2c3e4fc32525c122d97de77f5048 -m 'v0.3.9' && git push origin v0.3.9 && gh release create v0.3.9 --generate-notes
git tag -a v1.2.0 a359f38f47ab78d94890da3e45d96d11a61c08df -m 'v1.2.0' && git push origin v1.2.0 && gh release create v1.2.0 --generate-notes

Or create releases manually via the GitHub UI.

Prevent this in the future

If this is due to workflow file changes, avoid modifying them in the same commit as version bumps, or use a Personal Access Token with workflow scope.

See TagBot troubleshooting for details.

---

This issue was automatically created by TagBot. (Run logs)

[ChrisRackauckas-Claude]

Hi @ChrisRackauckas,

I investigated this TagBot issue. This is not a code bug but a permissions issue that requires manual intervention from a maintainer with push access.

Summary

TagBot was unable to create the following tags/releases because the commits likely modified workflow files, which the default GITHUB_TOKEN cannot operate on:

• v0.3.5 at commit 6956b64b - exists, needs tag and release
• v0.3.7 at commit 037240b9 - exists, needs tag and release
• v0.3.8 at commit e965e030 - exists, needs tag and release
• v0.3.9 at commit 292a753c - exists, needs tag and release
• v1.2.0 at commit a359f38f - exists, needs tag and release (most recent)

I verified all the commits exist in the repository and are valid targets for tagging.

Current State

The following tags are currently missing from the repository:

• v0.3.5, v0.3.7, v0.3.8, v0.3.9, v1.2.0

The repository currently has tags up to v1.1.5.

Action Required

A maintainer with push access needs to run these commands locally:

# Create and push all missing tags
git tag -a v0.3.5 6956b64b0ccb503fbe08fce87f8940e7ae9d31fe -m 'v0.3.5' && git push origin v0.3.5 && gh release create v0.3.5 --generate-notes
git tag -a v0.3.7 037240b9c06d528b49fe63289095ae0dd5162ebc -m 'v0.3.7' && git push origin v0.3.7 && gh release create v0.3.7 --generate-notes
git tag -a v0.3.8 e965e0302438bf1c21c285885bb0744ff480503b -m 'v0.3.8' && git push origin v0.3.8 && gh release create v0.3.8 --generate-notes
git tag -a v0.3.9 292a753cf55f2c3e4fc32525c122d97de77f5048 -m 'v0.3.9' && git push origin v0.3.9 && gh release create v0.3.9 --generate-notes
git tag -a v1.2.0 a359f38f47ab78d94890da3e45d96d11a61c08df -m 'v1.2.0' && git push origin v1.2.0 && gh release create v1.2.0 --generate-notes

Prevention

To prevent this in the future, consider:

1. Separating workflow file changes from version bumps into different commits
2. Or using a Personal Access Token with workflow scope for TagBot

I cannot create these tags myself as the ChrisRackauckas-Claude account doesn't have direct push access to the repository.