← Blog
AUTOMATION4 min read

Env writes, redeploys and secret changes now wait for one human approval each

Oct 19, 2026DekimuAI-generated

Vercel environment writes, redeploys and secret changes no longer wait on a to-do list for hand-typed commands. Each now becomes one Telegram card, approve or deny, and a CI job executes only what was approved. It shipped on Oct 18, runs from the main branch only, sits behind a kill switch, and keeps its invariants under test.

What was left to do by hand?

Earlier automation work had already turned merges, flag flips and digests into one-tap approvals. What remained was credential-bound: adding an environment variable, a dashboard redeploy, setting a repository secret, re-sealing a key. By October those were the last lines on a person's to-do list.

The target was simple: the only manual act left is approving a card. Provider-issued keys, logins and signatures stay with a person, because no automation can mint those.

Why does this not add new authority?

CI already held the write capability for its existing environment-sync and deploy-health jobs. The new job adds a human approval in front of that capability and nothing behind it.

Around it sit deny lists for the names that must never be written this way. Requests for them are refused before any card exists, so nobody is ever asked to approve a card that can only fail.

An edited request is a new id, and a new id is a new card.

How does an approval stay bound to what was approved?

The first design did not. Two fresh-context skeptic rounds and a code review each broke it. A re-attached approved row could replay an edited payload. A logged literal could forge result lines. Multi-target rows would have been shrunk silently.

The fixes are structural. A request id is derived from the hash of its content, so an approval can only belong to identical content. Before anything executes, the run takes a durable one-time marker for that id, so an id runs once, ever. Literal values are shown on the card, length-capped, and refused if they look like a credential. Generated secrets never reach a log. A request that would be silently shrunk is refused instead.

Does it work end to end yet?

Partly, at the time of writing, and the status matters. The first live approval, a harmless canary flag on one app, wrote the value correctly. The redeploy that followed was skipped by that project's build settings, which needed a fix of its own. The GitHub-side actions were held back until they had a narrowly scoped credential of their own, rather than borrowing a broader one.

AUTOMATION

This post was drafted by an AI system from Dekimu's public engineering record and published with automated checks, without per-post human editing.

← Back to blog