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
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.9.0 b62cfcd0d35e3b6d60e8ac041e82f24565c62ec4 -m 'v1.9.0' && git push origin v1.9.0 && gh release create v1.9.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)
TagBot could not automatically create releases for the following versions. This may be because:
.github/workflows/), whichGITHUB_TOKENcannot operate onVersions needing manual release
v1.9.0at commitb62cfcd0fatal: 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:
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
workflowscope.See TagBot troubleshooting for details.
This issue was automatically created by TagBot. (Run logs)