zeekay e7307c1984 ci: build the image and typecheck on the forge; drop GitHub-only automation
git.hanzo.ai collects .hanzo/workflows, so that is where the two lanes that
carry weight here now live:

  docker.yml   publishes ghcr.io/hanzoai/sentry. self-hosted/Dockerfile is
               Hanzo-branded and installs the wheel built from this source, so
               this repo does produce an artifact. It goes through the
               hanzoai/.github reusable rather than the hanzo.yml + hanzoai/ci
               pair because that Dockerfile needs dist/ populated first and the
               images: schema has no pre-build hook. The pre-build now installs
               node_modules before bdist_wheel, which setup.py's build_assets
               requires, and copies the curated requirements-frozen.txt instead
               of freezing the build venv.

  frontend.yml runs tsc over static/app, tests/js and fixtures/js-stubs. It is
               the widest gate needing only a checkout, and it covers what this
               fork changes: the TypeScript 7 tsconfig migration and the
               pkg.hanzo.ai npm route.

The other 29 workflows are removed. Most address GitHub or getsentry surfaces
that do not exist here: CodeQL and dependency-review are GitHub Advanced
Security; codecov_*, openapi, release, bump-sentry-in-getsentry and
getsentry-dispatch write into getsentry's org; lock, sync-labels,
label-pullrequest, fast-revert and sentry-pull-request-bot are issue and PR
bots; workflow-sanity calls a reusable that no longer exists.

The service-backed suites (backend, acceptance, migrations, monolith-dbs) are
dropped with their capability stated rather than stubbed: they need the
devservices stack — postgres, redis, clickhouse, kafka, snuba, symbolicator —
which this fleet does not run. mypy and jest are dropped as upstream surfaces:
they type and test upstream code, so a red result there points at code this
fork never touched. publish-dockerhub and self-hosted built and pushed
getsentry-namespaced images; docker.yml replaces them with the hanzoai one.
2026-08-13 21:05:04 -07:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2026-03-26 22:44:08 -07:00
2026-03-26 22:44:08 -07:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2026-08-04 17:21:55 -07:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00

Sentry

Users and logs provide clues. Sentry provides answers.

What's Sentry?

Sentry is a developer-first error tracking and performance monitoring platform that helps developers see what actually matters, solve quicker, and learn continuously about their applications.

Official Sentry SDKs

Resources

S
Description
Hanzo Sentry — Error tracking and performance monitoring
Readme
27 MiB
Languages
Python 61.4%
TypeScript 37.4%
HTML 0.4%
Less 0.4%
JavaScript 0.2%
Other 0.1%