TagBot: Manual intervention needed for releases
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 25/100
Research direction
The issue identifies the missing release as v1.0.0 at commit d2fd02c3 and points to the TagBot workflow. Start by checking that workflow’s permissions and the linked run logs. Done means the release is created and the workflow is configured with permission to push tags.
Written by the indexing model from the issue text.
Description
TagBot could not automatically create releases for the following versions.
Likely cause(s):
- The
GITHUB_TOKENlackscontents: writepermission to push tags
Versions needing manual release
-
v1.0.0at commitd2fd02c3
How to fix
Run these commands locally:
gh release create v1.0.0 --generate-notes
Or create releases manually via the GitHub UI.
Prevent this in the future
- Add
permissions: contents: writeto your TagBot workflow, or use a PAT/deploy key
This issue was automatically created by TagBot. (Run logs)
- Dominant language
- Julia
- Stars
- 0
- Forks
- 0
- Avg merge
- 39m
- Merged PRs (30d)
- 10
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from BioJulia/Workflows
-
TagBot trigger issueOpen
Difficulty 1/5 Under an hour Newbie friendliness 18/100
BioJulia/Workflows#11 · 22 comments ·
Maintainers usually reply within 1 day
All issues in BioJulia/Workflows
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
JuliaMath/BFloat16s.jl#138 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
-
ka_cpu_alloc_budget: the 320 B/launch KA 0.10 allowance is stale on KA 0.10.3 and hides allocationsOpenfound-by-agent
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
exanauts/SparseDirectSolver.jl#145 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Deltares/Wflow.jl#1145 · 1 comment ·
Maintainers usually reply within 1 day