Publish changelog entries from releases

changes.page hosts a running changelog of entries that announce new features, fixes, and updates to users. An agent can draft and create a new entry when a release ships, pulling the summary from wherever the team tracks release notes, such as a project management tool, and formatting it to the template the team has approved. Entries covering a change significant enough to need careful wording, such as a pricing change or a feature removal, are drafted but held for a person to review and approve before they go public.

Notify subscribers of new updates

Once an entry is published, changes.page can notify subscribers who follow the changelog, and an agent can trigger that notification according to a rule the team sets, such as only notifying for entries tagged as a major update rather than every minor fix. This keeps users informed about the changes that matter to them without flooding them with every small tweak. The agent confirms the notification went out and records it against the entry. If a notification fails to send or the subscriber list looks wrong, such as an unexpectedly small count, the agent flags it to a person instead of assuming it went through.

Tag and categorize entries

changes.page organizes entries by category or tag, such as new feature, fix, or improvement, which is how users filter the changelog to what matters to them. An agent applies the correct tag to a new entry based on the type of change and the taxonomy the team has set up, keeping the changelog consistently organized as entries accumulate over time. This avoids the drift that happens when different people tag entries inconsistently by hand. Entries that do not clearly fit an existing category, or that seem to span more than one, are left untagged and sent to a person to categorize.