Transparent + accessible.
Weekly release cadence
Stable + tested releases every Friday afternoon. Hotfixes shipped any time SEV-1+ requires.
Public version history
Every version number + date + summary public + persistent. URL-stable for sharing.
Subscription channels
RSS feed, email digest (weekly summary), Slack webhook (real-time), in-app banner for major changes.
API breaking changes
Breaking API changes flagged 30 days in advance. Versioning policy: v1 (stable), v2 (in development), legacy v0 maintained 12 months past deprecation.
Maintenance windows
Listed alongside release notes. 72-hour advance notice. Off-peak (Sun 02:00-06:00 ET).
Postmortems linked
Major incident postmortems linked from changelog. Published within 5 business days of any SEV-1+.
A clean handoff, in 4 steps.
Subscribe to channels
RSS, email digest, or Slack webhook. Pick what you want.
Read weekly releases
Every Friday: version, type, summary. Click through for details.
Track API deprecations
30-day advance notice for breaking changes. v1 stays stable.
Reference for audit
Public version history useful for SOC 2 audits + compliance reviews.
Common questions.
How often do you release?
Stable: weekly (Friday). Hotfixes: as needed for SEV-1+. Major versions: ~quarterly.
What's the difference between NEW · FIX · API · UI tags?
NEW = new capability. FIX = bug repair. API = endpoint or contract change. UI = user-interface change.
Will breaking changes happen without notice?
Never to API. UI may evolve without notice but we communicate major redesigns in advance.
How long do you maintain legacy API versions?
12 months past deprecation announcement. Enterprise customers get 18+ months on request.
Can I see changes BEFORE they go live?
Enterprise tier: yes, beta access to upcoming releases. Pro tier: opt-in via beta program for select features.
Where are security patches in the changelog?
Security patches noted as "FIX (SECURITY)" with CVE if applicable. Detailed disclosure 30 days after fix per responsible disclosure policy.
Does the changelog cover state SOS portal changes?
No: those are operational not product. They're communicated via in-app banner + email digest separately.
How do I subscribe?
RSS: file.business/changelog.rss. Email: subscribe in your BOS account settings. Slack: add webhook URL in Settings → Integrations.
Can I see who shipped each release?
Internal attribution; not public. Engineering team owns releases collectively.