Trellis

Acme platform team

Threads

Conversation

Retire the v1 billing webhook

Waiting on you

Retire the v1 billing webhook · today

AR
Alex Rivera · 09:12
Who is still calling the v1 billing webhook, and what would it take to retire it? Draft the deprecation notice while you are in there.
webhook-callers-oct.csvCSV · 18 KB
T
Trellis09:13

Twelve accounts still call v1, and 78% of that traffic is three of them — Northwind, Kestrel and Bluefin. The rest are under 400 calls a month each, so the long tail can move on its own schedule.

One real blocker: invoice.paid and invoice.voided have no v2 equivalent. Nothing can migrate off v1 until those ship. I have drafted the notice around a March 31 cutoff, which leaves six weeks after the v2 events land.

Artifact updated to v1

Drafted the notice — summary, timeline, and what callers have to change.

AR
Alex Rivera · 09:21
Good. Add the twelve accounts as a table so support can work down it, then let the three big ones know.

Artifact updated to v2

Added the caller table — twelve accounts, volume, and owner.

Email the three highest-volume callers

mail.send

One message each to Northwind, Kestrel and Bluefin, from platform-notices@acme.dev, with the notice attached.

{
  "to": ["ops@northwind.example", "api@kestrel.example", "dev@bluefin.example"],
  "subject": "Action needed: the v1 billing webhook retires March 31",
  "attach": "deprecation-notice.md"
}

Sends to three external addresses. Email cannot be unsent.

The run is waiting on the approval above. Answer it to carry on.

Trellis shows every call it makes. Nothing leaves the workspace without an approval.

Trellis command menu

Jump to a surface, open a thread, or run an action.