zeekay
2931d01d5a
A version written into a manifest is written into every manifest that wants it, which is how eslint came to exist in a hundred and four forms across this estate and how a package came to resolve twice at run time. The catalog moves the number out of the manifest: a manifest names the package, the workspace names the version. Four are held below their latest because the newer release cannot be used, and the reason is recorded rather than the version alone: @noble/hashes 2 renamed every subpath the web3 stack imports, @splinetool/runtime 2 depends on a package that was never published, @dynamic-labs 5.4.1 the same, and react-resizable-panels 3 points its types condition at the bundle.
Sentinel
Error tracking and performance monitoring for the Hanzo cloud. Sentinel receives events from your applications, groups them into issues, and tells you which ones are new, regressed, or getting worse.
Sentinel speaks the Sentry wire protocol, so the existing ecosystem of client SDKs reports to it unchanged — a DSN pointing at your Sentinel instance is the only configuration difference. There is no Sentinel-specific SDK to adopt, and none is planned; the protocol is the interface.
Running it
The deployed image is ghcr.io/hanzoai/sentry. Deployment is declared in the
universe repository and reconciled by Hanzo CD, like every other service.
Attribution and licensing
Sentinel is a fork of Sentry by Functional
Software, Inc., used under the Functional Source License, Version 1.0, Apache
2.0 Change License (FSL-1.0-Apache-2.0). See LICENSE for the
terms and NOTICE for attribution; both are required and are kept
current.
The FSL grants no trademark rights. "Sentry" is a trademark of Functional
Software, Inc., and this project is neither affiliated with nor endorsed by them.
Upstream marks are not used as branding here — where the name appears in this
codebase it refers to the module namespace (src/sentry/), the wire protocol, or
upstream attribution, none of which are brand usage.