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

• v1.54.0 at commit cd68a2d5
  • Error: Git command 'git -C /tmp/tagbot_repo_w4_fwlx_ push origin v1.54.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)

• v2.3.0 at commit ac519282
  • Error: Git command 'git -C /tmp/tagbot_repo_w4_fwlx_ push origin v2.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)

• v2.4.0 at commit 0eb1d91b
  • Error: Git command 'git -C /tmp/tagbot_repo_w4_fwlx_ push origin v2.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)

• v3.2.0 at commit 48bffa4f
  • Error: Git command 'git -C /tmp/tagbot_repo_w4_fwlx_ push origin v3.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)

• v3.3.1 at commit e277f850
  • Error: Git command 'git -C /tmp/tagbot_repo_w4_fwlx_ push origin v3.3.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)

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

• v3.5.1 at commit 9a1513d9
  • Error: Git command 'git -C /tmp/tagbot_repo_w4_fwlx_ push origin v3.5.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)

• v3.6.0 at commit d2d2b478
  • Error: Git command 'git -C /tmp/tagbot_repo_w4_fwlx_ push origin v3.6.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)

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

• v4.3.0 at commit 3e2c350c
  • Error: Git command 'git -C /tmp/tagbot_repo_w4_fwlx_ push origin v4.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)

• v4.4.0 at commit 688227cc
  • Error: Git command 'git -C /tmp/tagbot_repo_w4_fwlx_ push origin v4.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)

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

• v4.6.0 at commit 7aa1effb
  • Error: Git command 'git -C /tmp/tagbot_repo_w4_fwlx_ push origin v4.6.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 v1.54.0 cd68a2d5e29f381f52f29338065312745f606406 -m 'v1.54.0' && git push origin v1.54.0 && gh release create v1.54.0 --generate-notes
git tag -a v2.3.0 ac5192828fc7efe32e686c90b418aec035a02acd -m 'v2.3.0' && git push origin v2.3.0 && gh release create v2.3.0 --generate-notes
git tag -a v2.4.0 0eb1d91b1e98577f90043c9ed8344c9931d61adf -m 'v2.4.0' && git push origin v2.4.0 && gh release create v2.4.0 --generate-notes
git tag -a v3.2.0 48bffa4fbffa3dac3b0abc0fc9b15b6023ece098 -m 'v3.2.0' && git push origin v3.2.0 && gh release create v3.2.0 --generate-notes
git tag -a v3.3.1 e277f850996e58df1fc0894e39303a1cb7367f0c -m 'v3.3.1' && git push origin v3.3.1 && gh release create v3.3.1 --generate-notes
git tag -a v3.4.0 aae54650f290b95c091e7d14a4087119b92e3d06 -m 'v3.4.0' && git push origin v3.4.0 && gh release create v3.4.0 --generate-notes
git tag -a v3.5.1 9a1513d91907bcb2c1e050f682e6c9b5573db1b5 -m 'v3.5.1' && git push origin v3.5.1 && gh release create v3.5.1 --generate-notes
git tag -a v3.6.0 d2d2b478e171149faa87a6c59454ad4e656decb5 -m 'v3.6.0' && git push origin v3.6.0 && gh release create v3.6.0 --generate-notes
git tag -a v4.0.0 f1843f379b70d2ae0a1aa13eda3afeebc7e9ea78 -m 'v4.0.0' && git push origin v4.0.0 && gh release create v4.0.0 --generate-notes
git tag -a v4.3.0 3e2c350c9a8d73d159712704de64a02234fc39d7 -m 'v4.3.0' && git push origin v4.3.0 && gh release create v4.3.0 --generate-notes
git tag -a v4.4.0 688227ccdbd318432273f45a8d677678b2255453 -m 'v4.4.0' && git push origin v4.4.0 && gh release create v4.4.0 --generate-notes
git tag -a v4.5.0 fa8d57cca064c6d2afc9cd12792e08fd644f628d -m 'v4.5.0' && git push origin v4.5.0 && gh release create v4.5.0 --generate-notes
git tag -a v4.6.0 7aa1effb34b6fa3904361e692e623cc2e2890691 -m 'v4.6.0' && git push origin v4.6.0 && gh release create v4.6.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)