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.1.0 at commit 14a50c6b
  • Error: Git command 'git -C /tmp/tagbot_repo_twkzxglo push origin v0.1.0' 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)

• v0.2.0 at commit 7dcbb7a3
  • Error: Git command 'git -C /tmp/tagbot_repo_twkzxglo push origin v0.2.0' 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)

• v0.3.0 at commit 695101aa
  • Error: Git command 'git -C /tmp/tagbot_repo_twkzxglo push origin v0.3.0' 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)

• v0.4.0 at commit f8f89b9c
  • Error: Git command 'git -C /tmp/tagbot_repo_twkzxglo push origin v0.4.0' 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)

• v1.0.0 at commit 3545abde
  • Error: Git command 'git -C /tmp/tagbot_repo_twkzxglo push origin v1.0.0' 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.1.0 14a50c6b6abacbd22e93122f7934b0f787ca721f -m 'v0.1.0' && git push origin v0.1.0 && gh release create v0.1.0 --generate-notes
git tag -a v0.2.0 7dcbb7a389211db2c8574d440a0c337cbcc4d819 -m 'v0.2.0' && git push origin v0.2.0 && gh release create v0.2.0 --generate-notes
git tag -a v0.3.0 695101aa6dfbcbfa57ecc476103598198e0cb649 -m 'v0.3.0' && git push origin v0.3.0 && gh release create v0.3.0 --generate-notes
git tag -a v0.4.0 f8f89b9c6eae8d767de351705b2e752a5dc5d014 -m 'v0.4.0' && git push origin v0.4.0 && gh release create v0.4.0 --generate-notes
git tag -a v1.0.0 3545abde58cebfef24ca03a82aa628596c964084 -m 'v1.0.0' && git push origin v1.0.0 && gh release create v1.0.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)

Start with the five unchecked versions and the linked TagBot run logs, then review the provided git tag, push, and gh release commands. The work is done when each listed version has its tag pushed and a corresponding GitHub release created, or the GitHub UI confirms the releases already exist.