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

• v4.0.6 at commit e535733e
  • Error: Git command 'git -C /tmp/tagbot_repo_0cc6ahj0 push origin v4.0.6' 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)

• v4.0.7 at commit 5d4b35f2
  • Error: Git command 'git -C /tmp/tagbot_repo_0cc6ahj0 push origin v4.0.7' 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)

• v4.1.1 at commit 444f53ed
  • Error: Git command 'git -C /tmp/tagbot_repo_0cc6ahj0 push origin v4.1.1' 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 v4.0.6 e535733ebd483330f27497e8512b5def4cdba356 -m 'v4.0.6' && git push origin v4.0.6 && gh release create v4.0.6 --generate-notes
git tag -a v4.0.7 5d4b35f277b44f9dc56109374aa8975ced24aa23 -m 'v4.0.7' && git push origin v4.0.7 && gh release create v4.0.7 --generate-notes
git tag -a v4.1.1 444f53edaf60afb7ad61863121fc8b09dc300e51 -m 'v4.1.1' && git push origin v4.1.1 && gh release create v4.1.1 --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)