TagBot trigger issue #35
Triggered via issue
June 10, 2026 20:53
JuliaTagBot
Status
Failure
Total duration
3m 12s
Artifacts
–
Annotations
5 errors and 2 warnings
|
TagBot
Failed to release versions: v3.2.1
|
|
TagBot
Failed to process version v3.2.1: Git command 'git -C /tmp/tagbot_repo_35h5kqz5 push origin v3.2.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)
|
|
TagBot
Failed to push tag v3.2.1. If this is due to workflow file changes in the tagged commit, use an SSH deploy key (see README) or manually run: git tag -a v3.2.1 54318ad2b9054bee02298235107ed25307ce5a5c -m 'v3.2.1' && git push origin v3.2.1
|
|
TagBot
stderr: 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.
|
|
TagBot
stderr: 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.
|
|
TagBot
Could not create issue for manual intervention: Resource not accessible by integration: 403 {"message": "Resource not accessible by integration", "documentation_url": "https://docs.github.com/rest/issues/issues#create-an-issue", "status": "403"}
To fix permission issues, check your repository settings:
1. Go to Settings > Actions > General > Workflow permissions
2. Select 'Read and write permissions'
Or see: https://github.com/JuliaRegistries/TagBot#troubleshooting
|
|
TagBot
SSH key authentication failed: Permission denied. Verify the deploy key is added to the repository and has write access.
|