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.4.5` at commit `8f90ce1d`

## How to fix

Run these commands locally:

```bash
gh release create v0.4.5 --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](https://github.com/JuliaRegistries/TagBot#ssh-deploy-key)

---
*This issue was automatically created by TagBot. ([Run logs](https://github.com/JuliaWeb/GitForge.jl/actions/runs/28381912981))*

Start with the linked TagBot run logs to confirm why the release failed, then review the SSH deploy key setup described in the issue. Create the v0.4.5 release from commit 8f90ce1d using the listed GitHub CLI command or the GitHub UI; done means the release exists and the checklist item is resolved.

Written by the indexing model from the issue text.