TagBot: Manual intervention needed for releases

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.3.5 at commit 6956b64b
• v0.3.7 at commit 037240b9
• v0.3.8 at commit e965e030
• v0.3.9 at commit 292a753c
• v1.2.0 at commit a359f38f
• v1.2.1 at commit d5309538

How to fix

Run these commands locally:

gh release create v0.3.5 --generate-notes
gh release create v0.3.7 --generate-notes
gh release create v0.3.8 --generate-notes
gh release create v0.3.9 --generate-notes
gh release create v1.2.0 --generate-notes
gh release create v1.2.1 --generate-notes

Or 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)

Start with the linked TagBot run logs and verify the listed commits and release tags. Run the six shown gh release create ... --generate-notes commands, or use the GitHub UI; done when releases v0.3.5, v0.3.7, v0.3.8, v0.3.9, v1.2.0, and v1.2.1 exist.