Skip to content

Changelog

What was shipped

32 releases, by month and by area. Each entry leads to the page that details it, and to the documentation when it exists.

September 2026

  1. DeploymentsRollback in one gesture — or on its ownOn Deployments, a Vercel deploy that broke a check carries “Go back to the previous deploy”: PostShip repoints production to the last deploy it verified good. A per-project option does it without asking when a page that sells breaks on release.Read
  2. DeploymentsProduction actually serves this deployAfter every release, PostShip compares what your domain serves with the deploy URL. If the domain still loads the old version twenty seconds later — CDN cache, alias, DNS — you're told.Read
  3. AlertsNotifications on your phoneAlerts arrive as notifications on your phone or your browser, with no Slack or email between the failure and you. Settings → Notifications → On this device, with a one-click test.Read
  4. For your clientsMonthly report to your clientsOn the 1st of the month, the past month's summary — uptime, incidents, deploys, checks — goes out by email to the addresses of your choice. Team plan, with a preview to judge beforehand.Read
  5. AppA single button to monitor something“Monitor…” then the choice: a page, the pages that sell, a checkout journey, an API, a form, a scheduled task — each with what it checks. The project and URL menus were reworked, billing too.Read
  6. DeploymentsCloudflare Pages previewsVercel and Netlify were already there. Cloudflare Pages deploys are now recognised too, previews included.Read
  7. For your clientsRSS feed, embeddable banner and colourThe status page publishes an RSS feed, can be embedded in your own site as a banner, and takes on your brand colour.Read
  8. For your clientsCustom domain, certificate includedA status page at your address — status.yourdomain.com — with the certificate check that goes with it.Read
  9. AlertsCommands in Slack and Discord“/postship status” and “/postship check” answer in the room they're typed in, without leaving the conversation.Read
  10. AppTeam logWith several people on a project, “who muted the alerts?” now has an answer: the actions that change monitoring are dated and attributed.Read
  11. AutomationRead APIThe token used to trigger a check also reads the state of your projects, their URLs and their deploys. No write is possible with it.Read
  12. ChecksDead links and mixed content at deployOn every release, the home page's links are tested, and assets loaded over plain HTTP on an encrypted page are recorded. One line in the ship report, not one alert per link.Read
  13. AlertsMaintenance announced before it startsA planned maintenance shows on the status page ahead of time, rather than appearing as an outage the moment it begins.Read
  14. AutomationExport of what we billInvoices can be downloaded, in a format you can hand to an accountant.Read
  15. For your clientsRead-only link for a clientAn agency can show a project's state to its client without opening the account: a link that gives the state, and nothing that allows action. It expires after ninety days and is revoked in one click.Read
  16. AppThe account on a phoneThe seven settings sections fit in a row you had to push with a finger. They now open with one tap.Read
  17. DeploymentsThis week's previews on the OverviewHow many previews were checked this week, and how many are red. A count, not an alert: a failing pull request is not a site down.Read
  18. For your clientsPublic status pageEvery project can publish a status page at your address, kept up to date by the checks you've already set up. Your clients subscribe to it and are told without writing to you.Read
  19. DeploymentsPreviews checked before the mergeA pull request is checked on its preview URL, and the result shows on the commit. A Ship Score that's too low can block the merge.Read
  20. ChecksPurchase journey followed end to endBeyond a page that responds, PostShip follows a journey: the product page, the cart, the payment. A funnel that breaks in the middle doesn't look like an outage, and that's exactly what was missing.Read
  21. AutomationCommand line and GitHub ActionCheck from your terminal, or from a workflow, without opening the app.Read
  22. AlertsIncident roomWhen something breaks, one page gathers what we know: what failed, since when, what the last deploy changed.Read
  23. AutomationConnection to assistantsAn MCP entry point lets an assistant read the state of your projects — yours and those shared with you.Read
  24. DeploymentsThe before of a deploy, kept as an imageA deploy's social card is archived the moment it goes out. Weeks later, you can still show what the before looked like.Read
  25. DeploymentsT+2, T+8: the minutes after a deployAfter a production deploy, two automatic re-checks at T+2 and T+8 minutes catch what breaks once the cache and the CDN have settled.Read
  26. DeploymentsWhat changed, and Ship ScoreA deploy that replaces a page with “coming soon” or a 5xx error is detected and reported. Every production deploy also gets a Ship Score out of 100, with the explanation of what brought it down.Read
  27. DeploymentsDeploy historyThe Deployments page keeps track of every Vercel, Netlify or Cloudflare Pages trigger, with what broke or recovered since the previous one.Read
  28. AlertsAlert rules: confirmation, quiet hours, silenceRequire N consecutive failures before alerting, define quiet hours, or mute the alerts of a specific URL during a planned maintenance.Read
  29. ChecksBroken asset detection and money pathA JS or CSS file missing after a deploy is now detected, with a preset to monitor first the pages that take money (checkout, payment).Read
  30. ChecksSocial card previewEvery monitored URL shows a real preview of its Open Graph card — title, description, image — right in the dashboard.Read
  31. AlertsTelegram alertsDiscord and Slack were already there. Telegram joins as the third alert channel, with one bot per project.Read
  32. DeploymentsGitHub Check Run on every deployA Vercel production deploy now shows the result of the PostShip check directly on the GitHub commit.Read