Tripline

Changelog

What shipped.

  1. console

    Signup checks the tenant, and the pool fits loom

    Naming an organisation that already exists now says so instead of failing halfway through the claim. The Postgres pool on Cloud Run is sized for loom’s runners alongside ingest, so projections and alert delivery no longer contend with requests for connections.

  2. ingest

    DSN keys are Latchkey publishable keys

    The public key in every DSN is now minted by Latchkey on the project’s tenant and verified through it, with a ten-minute cache and a local index that keeps ingest up when Latchkey is not answering. Mint, revoke, expiry and last-used moved to the Latchkey console; -create-key mints another key for a project. The console adopted the house shell the same day.

  3. release

    Performance, team, and the port onto loom

    Transactions with a waterfall, p50 and p95 from bucket percentiles, and mobile vitals, kept for fourteen days. Tenant invitations, members and revocation on the Team page. Underneath, tripline moved onto loom: aggregates for projects and alert rules, records for issues and releases, series for events and transactions, and one journaled effect per notification.