A release goes out, and the public Releases board still shows only the last one. What shipped this time is a list of commit messages that mostly make sense to whoever wrote them.
After a successful deployment, your agent turns the relevant commit history into a plain-language summary and adds it to the release task.
What the agent starts with
A Releases board, shared publicly, with one card per version. The cards for 4.10 and 4.11 are written up. The card for 4.12 is there and empty.
And the range itself: fifteen commits between the v4.11 and v4.12 tags. Four of them changed something a user can see. The other eleven are reverts, dependency bumps and refactors — real work, none of it visible from outside.
The prompt
What comes back
Four commits became four lines. The eleven a user would never notice are not mentioned.
The card now reads like the two above it.
