Release Notes

Major updates Teleperson ships are summarized on the public Release Notes page. Each entry is tagged with the project it affects, and the page filters by project.

Project tags

Updates are tagged by which Teleperson surface they affect:

• Chatbot — the Teleperson browser extension and on-site chatbot UI (CurioBot, Ask AI, related assistants).
• Consumer App — the B2C consumer experience.
• B2B Company App — the operator and admin experience used by partner companies.

A single update can affect more than one project, in which case it shows multiple tags. Use the filter chips at the top of the Release Notes page to narrow the view.

How updates make it to the page

Release Notes are auto-published once a day for major updates only.

1. Daily publisher (07:00 UTC). A scheduled job reads commits to the Teleperson repo over the last 24 hours and keeps only the "major" ones — Conventional Commits prefixed feat: or feat(scope):, plus anything containing BREAKING CHANGE in the message body. Other commit types (fix:, chore:, docs:, refactor:, etc.) are ignored.
2. Project grouping. Each major commit is bucketed into one or more projects based on which files it touched. Files under extension/ and any chatbot/CurioBot/AskAI source go to Chatbot. The B2C consumer routes go to Consumer App. Everything else under src/ goes to B2B Company App.
3. Auto-publish. One Release Notes entry per project per day is inserted directly into the public list with is_published = true. The day's slug is derived from the SHA range so the same job running twice is a no-op.

Writing commits that show up

If you want a change to appear in Release Notes, write the commit subject in Conventional Commits form with a feat: prefix:

feat(chatbot): add follow-up question suggestions

Curio now offers three suggested follow-ups after each answer …

For a breaking change, include BREAKING CHANGE: in the body:

feat(b2b): replace company onboarding wizard

BREAKING CHANGE: the old `/CompanyOnboarding` route now redirects to
`/CompanyOnboardingWizard` …

Bug fixes (fix:) and chores (chore:) intentionally do not show up — that keeps the public Release Notes feed focused on real shipped value.