Reader subscriptions

A changelog people have to remember to visit is a changelog most people forget. On Pro, readers can subscribe by email straight from your public changelog page and get each entry as you publish it. Turn it on in the repo's settings, under Reader subscriptions.

How readers subscribe

With subscriptions enabled, your public changelog page — on the platform URL and on your custom domain — shows a subscribe form. A reader enters their email and gets a confirmation message; only after they click the link in it are they subscribed. This double opt-in is not optional: nobody can subscribe an address they don't control, and your list only ever contains people who actually asked.

What subscribers receive

One email per published entry — and one means one, ever:

• Publishing an entry emails your confirmed subscribers once.
• Editing the entry afterwards doesn't send another email.
• Archiving and re-publishing it doesn't either.
• If you use daily digests: manually publishing a digest before its day closes sends the email immediately with the day's changes so far, and it will not be emailed again when the day is finalised. See How drafts are generated.

Emails come from ChangelogPilot's sending address, with your changelog identified in the subject and body.

Unsubscribing

Every email carries a one-click unsubscribe link that works without signing in, plus the standard list-unsubscribe header mail clients surface as their own unsubscribe button. Addresses that hard-bounce are suppressed automatically.

Limits

Pro includes up to 10,000 confirmed subscribers per repo. Once a repo is at the cap, new subscription attempts are refused.

Turning it off, and downgrades

Switch subscriptions off and the form disappears from your page; your subscriber list is kept, and switching back on picks up where you left off. The same applies to a downgrade: sends stop, the list stays, and everything resumes on re-upgrade. We never delete your subscribers for you.