release
Releasing agent-communications
Every package in scripts/packages.mjs goes to npm together, in that order — today @agentcomms/core,
@agentcomms/gmail, @agentcomms/gmail-mcp, @agentcomms/resend, @agentcomms/slack and @agentcomms/whatsapp
(node scripts/packages.mjs prints the list). That file is the one list, derived from the channels' manifests: the
workflow, the local script, sync-versions, verify:packages and the licence notices all read it, and a test fails if
a publishable package is missing.
Pushing a v* tag publishes them. That push is the irreversible act; there is no confirmation after it.
The one thing to understand first
npm keeps a published version for ever. The 72-hour unpublish window is not a fix once somebody has installed it, and the name and version are burned either way. There is no rollback. A bad release is corrected by publishing a higher version, never by replacing the one that went out.
Everything below follows from that.