v1.3.0: native Gitea + Forgejo webhook support #1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "dual-forge-support"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Accept either X-Gitea-* or X-Forgejo-* headers (event, signature,
delivery) via _first_header(), preferring the Gitea names so existing
deployments behave identically. HMAC verification runs against whichever
signature header the forge sends; payloads are byte-identical today.
Rename GITEA_WEBHOOK_SECRET -> WEBHOOK_SECRET, keeping the old name as a
deprecated alias resolved in create_app(). Neutral naming throughout:
project apprise-forge-bridge, startup log, docker-compose service, and
Docker Hub image apprise-forge-notifications. README/Claude.md/SECURITY.md
updated for both forges; SECURITY.md base-image ref corrected to 3.14.
Add 5 tests (Forgejo headers, both-vendor, Forgejo bad-sig, dual
missing-event, legacy-secret alias) -> 80 total.
Co-Authored-By: Claude Opus 4.8 noreply@anthropic.com