JuliaDiff / JuliaDiff/FiniteDifferences.jl
TagBot: Manual intervention needed for releases
Open
Nobody has claimed this yet.
tagbot-manual
- Dominant language
- Julia
- Stars
- 318
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
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.12.34at commit02217d1e
How to fix
Run these commands locally:
gh release create v0.12.34 --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 linked TagBot run logs and confirm that release creation failed because the SSH deploy key is unavailable. Create the v0.12.34 release from commit 02217d1e using the documented command or GitHub UI, then verify that the release exists. Check the deploy-key setup link if preventing recurrence is in scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github, github-actions, julia
- Domain
- ci-cd, devops, release
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100