Repository navigation
TagBot: Manual intervention needed for releases #694
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
-
v0.6.12at commit17a1e7fe
How to fix
Run these commands locally:
gh release create v0.6.12 --generate-notesOr 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)
Activity
CarloLucibello commentedon Jul 31, 2026
Fixed — the missing release is now published: GraphNeuralNetworks-v0.6.12.
What happened: During the monorepo re-tagging, TagBot (subdir
GraphNeuralNetworks) noticed that the registered commit for v0.6.12 (17a1e7fe, theUpdate Project.tomlbump) differs from the commit the legacy unprefixedv0.6.12tag points to (dafe3aef, its parent). It therefore treated v0.6.12 as untagged, pushed the annotated tagGraphNeuralNetworks-v0.6.12via the SSHDOCUMENTER_KEY, but then got403creating the GitHub release (run logs). Because the tag then existed, TagBot considered the commit tagged and never retried, leaving the release stranded.Fix: created the release from the existing tag (non-latest, so
GNNLux-v0.2.0stays the repo's latest release), reusing the incremental changelog from the originalv0.6.12release rather than the cumulative one embedded in the tag message.No workflow change needed: the repo's default
GITHUB_TOKENis already set to read/write, so future releases are unaffected — this was a one-off straggler from the historical commit-hash mismatch. All other prefixed main-package releases (v0.6.22,v0.6.23,v1.0.0,v1.1.0) are already present.