Skip to content

TagBot trigger issue #44

TagBot trigger issue

TagBot trigger issue #44

Triggered via issue January 3, 2026 12:05
@JuliaTagBotJuliaTagBot
commented on #1 1bd9129
Status Failure
Total duration 3m 49s
Artifacts

TagBot.yml

on: issue_comment
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 3 warnings
TagBot
Failed to release versions: v0.5.0, v0.5.1
TagBot
Failed to process version v0.5.1: Git command 'git -C /tmp/tagbot_repo_nlwsoy3m push origin v0.5.1' failed
TagBot
Failed to push tag v0.5.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 v0.5.1 1bd91290ee317a1512fad5d69332b378123b9d59 -m 'v0.5.1' && git push origin v0.5.1
TagBot
Failed to process version v0.5.0: Git command 'git -C /tmp/tagbot_repo_nlwsoy3m push origin v0.5.0' failed
TagBot
Failed to push tag v0.5.0. 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 v0.5.0 1d2ba9eab074280b4250752abc9757ded11ce513 -m 'v0.5.0' && git push origin v0.5.0
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
No registry pull request was found for this version
TagBot
SSH key authentication failed: Permission denied. Verify the deploy key is added to the repository and has write access.