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.7.3 at commit abf19df1
  • Error: Git command 'git -C /tmp/tagbot_repo_bzxt5w4u push origin v0.7.3' failed: git@github.com: Permission denied (publickey).
    fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists. (configure SSH deploy key or switch to https with PAT)

How to fix

Run these commands locally:

git tag -a v0.7.3 abf19df1a854f33933ffc5bbbe5c9453aba76612 -m 'v0.7.3' && git push origin v0.7.3 && gh release create v0.7.3 --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 with the TagBot run logs and the .github/workflows/ history for the v0.7.3 release at commit abf19df1. Check whether the tag exists and whether the release was created; done means the v0.7.3 tag and GitHub release are available, using the listed local commands or the GitHub UI.