Skip to content

Deploy Center 0.8.0

Choose a tag to compare

@Pschmetzer Pschmetzer released this 10 Nov 07:29
8a2e9d2
  • Mac widgets ship with the app (small: PRs waiting; medium: top projects and the saving). Add them from the widget gallery.
  • deploys: each platform is one file, providers/vercel.sh and providers/render.sh, behind one contract (docs/PROVIDERS.md). Nothing changes for Vercel and Render users. New: deploys list --json (every project on every platform), deploys providers [--json], deploys providers enable|disable <p> (Vercel and Render are on by default, any later platform is off until turned on), and names as render:web. Every json entry has a phase (queued, building, ready, failed, canceled). render deploy-json --preview is refused instead of deploying production.
  • providers/hook.sh (generic deploy hook) follows the same contract: off until deploys providers enable hook, then deploys hook add|remove|list|deploy route through deploys. deploys hook status <name> keeps its JSON; its doctor fields are hookReady, hookStore, hookCurl and hooks.
  • Auto-deploy guard (deploys guard, Settings → Auto-deploy guard): every 30 minutes it turns auto-deploy off again wherever it is on without an allowance, and notifies. deploys autodeploy allow <platform> <project>|--all <hours> allows it for a while (emergencies); deploys vercel|render autodeploy-on turns it back on. The first run is a dry run.
  • Window: each row shows what autofix does ("Claude is fixing", fix PR open/merged, "deploy the fix"), a "Fix with Claude" button on failed rows (deploys autofix --only), allowance badges, and the count in the menu bar.
  • Self-update moved to Updater.swift: checks the folder is writable, swaps with a rollback, accepts only the same Team ID and no downgrade, runs off the main thread, asks before quitting during deploys, cleans up on every path.
  • Fixed: after a deploy, rows return to idle, so new commits count as waiting again; "today" is the local day, not UTC; notifications are asked for at the first one, not only at the first deploy.
  • Fixed: a timeout ends the whole process group; a deploy timeout no longer causes a double deploy; cancel cannot leave a row running forever; a load error keeps the cached list and shows above it.
  • Build log: secrets are masked before "Copy for Claude", fewer false error lines, ANSI codes removed; one broken project no longer fails the whole list.
  • Journal and saved state live in Application Support; CSV export is safe in spreadsheets.
  • UI: demo mode masks names everywhere; one collapsible notice area; settings in sections; Help menu, Dock badge, VoiceOver labels and actions, clearer empty states, raw states like build_failed translated, build log selectable across lines.
  • deploys: a Render read error no longer marks services changed, an unreachable API is an error instead of "Nothing to deploy", changed --platform X --json keeps the filter, only a real missing ancestor counts as rewritten history; --help, --version, where, history, forget-key, deploy --wait; timeouts and retries for Render.
  • Release: release.sh passes --repo and --target, checks the tree, can publish an existing build; the cask depends on jq, quits the app on uninstall and explains brew trust and --appdir.
  • Security: Autofix log masking keeps Authorization: Bearer tokens out (they used to pass, and a $1[masked] replacement emptied other matches) and now also masks AWS secret keys, Stripe, GitLab, npm and Google keys, private key blocks, --token arguments and *_KEY= values.
  • Security: a Vercel team id or a temp folder path can no longer run as shell code in costs, vercel json, render json and triggers; team ids are checked. Project and repo names reach jq as --arg, never inside a filter; JSON from GitHub file names is built by jq.
  • Security: project names and deploy ids with / ? # & % \ or control characters are refused before any API call; logs takes digits only for the line count; autofix set-token refuses tokens with spaces or quotes.
  • SECURITY.md: threat model, what is sent where, rules for new code.
  • GitLab as a source next to GitHub (gitlab.com and self-managed): waiting commits, merged and open merge requests, and details, through glab or GITLAB_TOKEN (+ GITLAB_HOST). Same JSON as for GitHub; doctor reports gitlabCli and gitlabLoggedIn. See docs/GITLAB.md.
  • The CLI installs on its own (macOS, Linux, WSL, CI): curl -fsSL https://deploycenter.app/install.sh | sh (SHA-256 checked, ~/.local/bin, sudo only for a prefix that needs it; --prefix, --version, --uninstall) or brew install pschmetzer/tap/deploys. Releases carry deploys-cli-<version>.tar.gz and checksums.txt next to the app zip. See README-CLI.md.
  • Claude Code plugin in integrations/claude-code/: a skill, /deploys-* commands and a read-only reminder after git push; install with /plugin marketplace add Pschmetzer/deploy-center. See docs/CLAUDE-CODE.md.
  • providers/amplify.sh: AWS Amplify Hosting, opt-in. Auto-build off per branch, deploy (start-job RELEASE, with --sha), cancel, logs, and rollback by rebuilding an earlier commit, through the aws CLI. See docs/providers/amplify.md.
  • Claude in the app (opt-in, off by default, your own Anthropic API key): Ask Claude in the detail sheet and build log explains a failed build (with Hand to Autofix), writes plain release notes in English or German, and answers "Is this safe to ship?". Settings → Claude in the app: key in the keychain, Verify, model, monthly token cap and usage. CLI: deploys ai explain|notes|ship <project>. Only masked text is sent; the masker now also hides email addresses. See docs/CLAUDE.md.
  • examples/claude-pr-ship-check.yml: on each PR, Anthropic's Claude Code GitHub Action comments "What this ships" from deploys changed --json.
  • integrations/mcp/: an MCP server for AI coding agents. Read-only by default (changed, status, explain, notes, logs, doctor); deploy and rollback of one project per call only with DEPLOYS_MCP_ALLOW_DEPLOY=1.
  • Safe deploys (see docs/SAFE-DEPLOY.md): deploy-changed --when-green [--wait 30m] deploys only commits whose CI passed (and waits for running checks); deploys verify <project> checks the site after a deploy and rolls back after a countdown; window.json closes deploy windows (--force "why" goes to the journal); deploys risk <project> scores the waiting diff green/yellow/red. New: deploys deploy <project>, deploys ci, deploys window.
  • App: "Only when checks are green" in the deploy confirmation, "Roll back if the check fails" per project in the details (a countdown notification with Cancel), a warning with "Deploy anyway…" inside a closed deploy window, and a red dot for risky changes.
  • Team mode, without a server (docs/TEAM.md): a shared deploy-center.json in each repo (project → repo/branch, health paths, deploy window, ignored projects, groups, approvals, observers), read with gh and cached, merged below this Mac's own files. deploys config [--json] shows each value and where it came from; schema in docs/deploy-center.schema.json.
  • Observer mode: DEPLOYS_READONLY=1, ~/.config/deploys/readonly (deploys readonly on|off, Settings → Team), or a login in observers. Every command that changes something is refused; the app hides its deploy buttons and shows "Observer".
  • Two-person rule (optional per project): a production deploy needs an approving PR review or a deploy-approved-by:<login> label from someone else, on the exact commit, which is then pinned. --force "reason" overrides and is journaled (deploys team journal).
  • deploys deploy <project>|<group>: one project on either platform, or a group in order, each waiting for the one before to be live.
  • Fixed: file ages on Linux (stat), which the start lock and the Vercel team cache depend on.
  • Window: the tabs come from the enabled providers (deploys providers --json; Vercel and Render with an older script). One provider has no tabs, two or three a segmented control with "All", four and more a menu; ⌘1, ⌘2 … follow the order, "All" takes the next digit (⌘3 with Vercel and Render, as before).
  • Settings → Platforms: a switch per provider. Vercel and Render are on; others say "coming soon" until the script reports them, and switching runs deploys providers enable|disable.
  • Calmer window: one summary line ("12 PRs waiting · $41 saved") instead of the waiting banner and sparkline; the cost bar is one number that opens a Costs sheet with the chart and "Share the saving"; "updated hh:mm" is in the reload tooltip; rows show one figure and sit under a small repo header instead of "same as above"; the footer has "More" (select all changed ⌘A, clear, preview deploy, history, messages) next to "Deploy N"; the row menu is Deploy, Build log, Open site, More.
  • Agent digest (integrations/digest/): once a day, what waits per project with agent and human commits apart, pull requests and risk hints, as Markdown, an issue and a webhook message with an approve button. An example workflow deploys only the projects a listed person approved (button or deploy-approved label).
  • deploys details: each commit carries its Co-Authored-By trailers as coAuthors.
  • Savings, all marked as estimates (≈) with the method in the JSON: deploys simulate [--days 30] --json counts pushes to each deploy branch (GitHub) times the project's average build and puts "auto-deploy ≈ X a month" next to "once a day ≈ Y"; deploys ledger --json counts the pushes since auto-deploy was turned off that never built, in dollars, Vercel build minutes and Render pipeline minutes (logic in lib/savings.sh). The app has a Simulator sheet (a banner before anything is turned off, and Settings > Costs) and a Ledger ("≈ $X saved since …", per project, skipped pushes, share card).
  • App: command palette (⌘K). Fuzzy search over the actions (deploy all changed, reload, stop all, journal, settings, costs) and per project deploy, log, open, dashboard, rollback and notes; recent commands first. Deploys and rollbacks ask first, as in the window. Optional global ⌥⌘K under Settings → Advanced (off by default).
  • deploys autofix: a failed build (Vercel ERROR, Render build_failed) is handed to a Claude Code routine that opens a fix PR; after the merge it only notifies you; deploying stays a click (#51). Caps, no duplicates, never merges. See docs/AUTOFIX.md and scripts/autofix.plist.example.
  • deploys status --json carries each project's repo (owner/name), so an editor can match it to the open folder.
  • New: a VS Code / Cursor / Windsurf extension in integrations/vscode/ (waiting count in the status bar, a project tree, deploy with confirmation, build log and "Copy for AI").
  • deploys logs <project> --id <deploy> reads the log of one deploy; vercel json and render json carry latestId and latestSha of the newest attempt.

Notarized by Apple: opens without a warning.

SHA-256 of the zip: ec5919366759021bb5d803a0652c7bb4118711cd423bc49803b4b76cae1feb91

The CLI on its own (macOS, Linux, CI): curl -fsSL https://deploycenter.app/install.sh | sh or brew install pschmetzer/tap/deploys. SHA-256 of deploys-cli-0.8.0.tar.gz: e6f08ad751545cfd28429950ed0308f5c2fb05a486e7cf5bed68e9ddd37dd272