Repository navigation
TagBot: Manual intervention needed for releases #56
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.1.11at commit8f91b887
How to fix
Run these commands locally:
gh release create v0.1.11 --generate-notesOr 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)
Activity
IanButterworth commentedon Oct 26, 2026
Claude:
TagBot doesn't look stuck any more: the v0.1.11 release now exists (created 2026-08-14), so this issue can probably be closed.
What is missing is a registration. #53 bumped master to 0.1.12, but nobody has run
@JuliaRegistrator registeron it, so General still ends at 0.1.11. PkgEval tests the registered version, so ExprTools still fails on Julia nightly (1.15-DEV), including the semicolon tests that #53 fixes. The constructor tests also need #57 (Core.TypeEq). Could a maintainer merge #57 and then register master?Written with Claude Code (Opus 5.5).
JuliaRegistrator commentedon Oct 26, 2026
Error while trying to register: Register Failed
@IanButterworth, it looks like you are not a publicly listed member/owner in the parent organization (JuliaTesting).
If you are a member/owner, you will need to change your membership to public. See GitHub Help