maziggy 4343bd60b1 fix(notifications): honest UA + Cloudflare-challenge detection on ntfy (#1534) ...

The notification service's httpx client was the only outbound client in
  the codebase still leaking python-httpx/<version> as User-Agent; all
  other clients identify as Bambuddy/1.0 since the May 2026 compliance
  pass. Bring it in line.

  The reporter's ntfy server was behind a Cloudflare Tunnel and CF returned
  its JS challenge page (Just a moment...) to every API request — confirmed
  by reproducing the same 403 with curl. Cloudflare can't be solved from a
  backend, so add detection for the challenge shape (Server: cloudflare or
  cf-mitigated header, or <!DOCTYPE html>...Just a moment... body) and
  return an actionable error message that points at the real fix on the
  user's CF side instead of dumping the raw HTML.

  Normal 403s (auth failures with plain text bodies) still surface the
  original body so genuine errors stay debuggable.

2026-05-26 11:21:03 +02:00

..

app

fix(notifications): honest UA + Cloudflare-challenge detection on ntfy (#1534)

2026-05-26 11:21:03 +02:00

tests

fix(notifications): honest UA + Cloudflare-challenge detection on ntfy (#1534)

2026-05-26 11:21:03 +02:00

__init__.py

…

=0.9.0

fix(test): stop sys.modules-deleting backend.app.main in test_code_quality

2026-05-24 12:51:24 +02:00