Skip to content

Release console

Ship a build of a notes app to three environments: watch it build, read the logs as they stream, roll back, and stage flag changes, all from the keyboard if you like.

fieldnote-web

fieldnote/web

Environment
Healthy
Command bar ⌘K

Next up · Production

Fix double submit on the billing form

a3f9c21Priya Ramanmain

Not started0.0s
  1. Build

    next build, remote cache

    Queued~3.0s
  2. Test

    214 unit, 38 integration

    Queued~2.1s
  3. Deploy

    iad1, fra1, sin1

    Queued~1.6s
  4. Verify

    health checks, smoke tests

    Queued~1.1s

Deployments

Production

4 total
  • Cache the notebook tree per workspace

    7c1e0a2Mei Lin42m ago

    Current

    Built in 9s · iad1 fra1 sin1 · fieldnote.app

  • Fix caret jump when pasting rich text

    4b9d2e8Priya Raman3h ago

    Built in 9s · iad1 fra1 sin1 · fieldnote.app

  • Add billing portal link to settings

    e3f6017Ada Brennan1d ago

    Built in 9s · iad1 fra1 sin1 · fieldnote.app

  • Lazy-load the PDF exporter

    0a8c5d3Jonah Okafor2d ago

    Built in 8s · iad1 fra1 sin1 · fieldnote.app

Logs

Live

No run yet. Press Deploy, or D, and the build streams here.

Feature flags

Rollout

All changes saved
  • New checkoutcheckout-v2

    Single-page checkout with saved cards

    25%
  • Edge image resizingedge-image-resize

    Resize uploads at the edge, not the origin

    100%
  • Note summariesnote-summaries

    Two-line summaries in the note list

    off
  • Offline syncoffline-sync

    Queue edits locally when the connection drops

    5%
Simulated backend · runs in your browser · time runs about eight times fastPress ⌘K for everything

Decisions

How it's built

  1. 01

    Waiting is described, not decorated

    The deploy button only says a run is slow once it passes the slowest normal run, and each step compares itself with its own typical time, so “slow” appears on the step that is actually slow (a cold build cache), with the reason in the logs. A failed test stops the pipeline, names the file and line, and the same button becomes Retry.
  2. 02

    Logs follow you until you leave

    The log pins to the newest line only while you are at the bottom. Scroll up to read and it stays put, counting what arrived; one button takes you back. It is a focusable log with live announcements off; a separate polite region says only the step changes, so a screen reader is not read two hundred lines.
  3. 03

    Old logs load without a flash

    Opening an older deployment’s logs goes through Latency adapt: a fast answer shows no placeholder at all, a skeleton shaped like log lines appears after 150 ms, and past two seconds the region says it is still waiting and offers a Cancel that really aborts the request.
  4. 04

    Keyboard first, never trapped

    Everything is in the command bar, and D and L work as single keys except while you are typing or inside a select. Rolling back asks inline, moves focus to the confirm, and Escape puts focus back where it was. Flag edits are staged and counted until you save, because a toggle that ships to production on click is a trap of its own.