TagBot: Manual intervention needed for releases

[github-actions]

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.2.1 at commit d1deb07b
• v0.2.2 at commit 5e7b4c25
• v0.2.3 at commit 54dbe2cf
• v0.2.4 at commit 83d0fa39
• v0.2.5 at commit c99a84df

How to fix

Run these commands locally:

gh release create v0.2.1 --generate-notes
gh release create v0.2.2 --generate-notes
gh release create v0.2.3 --generate-notes
gh release create v0.2.4 --generate-notes
gh release create v0.2.5 --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)

[ChrisRackauckas-Claude]

@ChrisRackauckas This TagBot issue requires manual intervention to create the missing tags and releases for versions v0.2.1 through v0.2.5.

I verified:

• All 5 commits referenced in the issue exist in the repository
• Tags v0.2.1-v0.2.5 are indeed missing (existing tags: v0.0.1, v0.0.2, v0.1.0, v0.2.0, v1.0.0)
• Releases for these versions are also missing

However, I don't have push permissions to create tags directly. Someone with repository write access needs to run the following commands:

git tag -a v0.2.1 d1deb07baf7f2fc1113c57bf4d7a79b8372aa69f -m 'v0.2.1' && git push origin v0.2.1 && gh release create v0.2.1 --generate-notes
git tag -a v0.2.2 5e7b4c2533961133649b42e0fb3abf7cf7801be4 -m 'v0.2.2' && git push origin v0.2.2 && gh release create v0.2.2 --generate-notes
git tag -a v0.2.3 54dbe2cf90b1d2480c44301c5065ff01bf7665ec -m 'v0.2.3' && git push origin v0.2.3 && gh release create v0.2.3 --generate-notes
git tag -a v0.2.4 83d0fa391baf6dffe24bfd8402b1545045792166 -m 'v0.2.4' && git push origin v0.2.4 && gh release create v0.2.4 --generate-notes
git tag -a v0.2.5 c99a84dfceedf7cdfebe83b84fd6946deeacac38 -m 'v0.2.5' && git push origin v0.2.5 && gh release create v0.2.5 --generate-notes

Alternatively, you can create releases via the GitHub UI.

Note: The issue mentions that this happened because 'git push origin $tag' failed. This could be due to:

1. Workflow file changes in those commits (which GITHUB_TOKEN cannot push)
2. Network/API errors

To prevent this in the future, consider using a Personal Access Token with workflow scope for TagBot as mentioned in the issue.