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.3` at commit `b039d3a3`
- [ ] `v0.3.4` at commit `4118229c`

## How to fix

Run these commands locally:

```bash
gh release create v0.3.3 --generate-notes
gh release create v0.3.4 --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/FluxML/DataAugmentation.jl/actions/runs/28572558305))*

Start with the linked TagBot run logs and check the repository's deploy-key setup against the SSH deploy key setup guide. Create v0.3.3 and v0.3.4 with the supplied gh commands or GitHub UI, then confirm both releases are published and the deploy key is configured for future runs.

Written by the indexing model from the issue text.