TagBot: Manual intervention needed for releases

TagBot could not automatically create releases for the following versions.

Likely cause(s):

• A network or API error occurred
• The commits modify workflow files, which GITHUB_TOKEN cannot push

Versions needing manual release

• v0.8.18 at commit 3aa8b6a5
• v0.8.22 at commit 339392a9
• v0.8.47 at commit f2559acd
• v0.8.48 at commit 17582f13
• v0.8.49 at commit 42a2c04d
• v0.8.50 at commit 8bf6d19a
• v0.8.51 at commit e3b750fb
• v0.9.3 at commit 7b2081df
• v0.9.4 at commit d5ff57df
• v0.9.5 at commit 414e1c5c
• v0.9.6 at commit 341b9602
• v0.9.10 at commit 65c88d36

How to fix

Run these commands locally:

gh release create v0.8.18 --generate-notes
gh release create v0.8.22 --generate-notes
gh release create v0.8.47 --generate-notes
gh release create v0.8.48 --generate-notes
gh release create v0.8.49 --generate-notes
gh release create v0.8.50 --generate-notes
gh release create v0.8.51 --generate-notes
gh release create v0.9.3 --generate-notes
gh release create v0.9.4 --generate-notes
gh release create v0.9.5 --generate-notes
gh release create v0.9.6 --generate-notes
gh release create v0.9.10 --generate-notes

Or create releases manually via the GitHub UI.

Prevent this in the future

• See TagBot troubleshooting for details

This issue was automatically created by TagBot. (Run logs)

Start with the linked TagBot troubleshooting guide and the referenced GitHub Actions run logs, then review the twelve listed versions and commits. Use the provided GitHub CLI commands or the GitHub UI for each version; done means every listed release exists with generated notes.