TagBot: Manual intervention needed for releases

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.14 at commit a319cb47
  • Error: Git command 'git -C /tmp/tagbot_repo_r6uxavng push origin v0.3.14' failed

How to fix

Run these commands locally:

git tag -a v0.3.14 a319cb47a5633b8d43d9c282b3c11ee71d912c77 -m 'v0.3.14' && git push origin v0.3.14 && gh release create v0.3.14 --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)

Start by checking the TagBot run logs linked in the issue and the TagBot troubleshooting guidance for workflow-file changes. Verify whether tag v0.3.14 exists at commit a319cb47a5633b8d43d9c282b3c11ee71d912c77, then use the documented local commands or GitHub UI. Done means the tag and GitHub release for v0.3.14 are present.