[HMA] Update image reference due to org name change

Merged
JU
3d ago
+4-4

Context & Requests for Reviewers

Updates the image location for HMA from facebook org to meta as they have renamed the public org.

Checklist

Only check items that apply to this PR; leave the rest unchecked.

  • If you changed anything user-facing (i.e. user interface or APIs):
    Did you update related docs?

  • If the change is notable (refer to Keep a Changelog conventions):
    Did you update CHANGELOG.md?

  • If you changed db/src/scripts/** and used CREATE TABLE, ADD COLUMN, or ALTER COLUMN:
    Are as many columns marked NOT NULL as possible? If some columns can sometimes be null depending on other columns, are there CHECK constraints capturing those relationships, and are these also reflected using unions in the associated Kysely types?

  • If you added a new signal in server/services/signalsService/signals/**:
    Did you classify every error case as a permanent error (SignalPermanentError, no retry) or a normal error (retryable)? Any case where the signal can't determine a score should be a SignalPermanentError.

Summary by cubic

Updates HMA references from the facebook GitHub org to the renamed meta org across the Dockerfile, docs, and env example. The Docker image is now pulled from ghcr.io/meta/threatexchange/hma:1.2.1; the docs and comment updates are reference-only and have no runtime impact.