JuliaDebug / JuliaDebug/Debugger.jl
TagBot: Manual intervention needed for releases
Open
Beginner friendly
Nobody has claimed this yet.
tagbot-manual
- Dominant language
- Julia
- Stars
- 514
- Forks
- 50
- Avg merge
- 9d 9h
- Merged PRs (30d)
- 1
Description
TagBot could not automatically create releases for the following versions.
Likely cause(s):
- The SSH deploy key is not configured or not added to this repository's deploy keys (Settings → Deploy keys)
Versions needing manual release
-
v0.8.1at commit7f4a64df -
v0.9.0at commite44e580e -
v0.9.1at commit1ac6f772 -
v0.9.2at commit7e3ae2f8 -
v0.9.3at commit4d007718
How to fix
Run these commands locally:
gh release create v0.8.1 --generate-notes
gh release create v0.9.0 --generate-notes
gh release create v0.9.1 --generate-notes
gh release create v0.9.2 --generate-notes
gh release create v0.9.3 --generate-notes
Or create releases manually via the GitHub UI.
Prevent this in the future
- Add the TagBot public key to this repository's deploy keys — see SSH deploy key setup
This issue was automatically created by TagBot. (Run logs)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the listed versions and commits in the issue, then run the provided gh release create commands or use the GitHub UI. Verify that releases v0.8.1 through v0.9.3 exist with generated notes, and review the TagBot SSH deploy key setup if preventing future failures is part of the task.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github-actions, julia
- Domain
- ci-cd, release
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 72/100