The tag is live. Changelog, migration guidance, and user docs still describe last week. Point Looper at the repo. It reads the triggering release, names what users will notice, and updates only the stale documentation sections.
Pro is $19/mo for 10 loops. Two free loops, no card, if you want to try first.
A solo operator cuts a release, then morning still shows yesterday’s notes. Users hit a breaking change with no migration path. Looper is the loop that syncs the writing to the ship.
The GitHub release exists. The notes still list last sprint, or they copy the tag name and stop there.
CHANGELOG.md missed the merged change. Added, Changed, and Removed never caught the user-visible behavior.
Breaking changes shipped without a path. Operators discover the new requirement in production, not in the docs.
A full docs rewrite hides the stale sections. The next reader cannot tell what this release actually changed.
Same cycle every run. You set the schedule. Looper treats the release as the source of truth for the docs that should move.
Read the triggering release or merged change, the user-visible behavior, and the current changelog and docs.
Name breaking changes, migrations, and operational notes. Mark only the documentation sections that are now stale.
Update those sections — not the whole wiki. Keep release notes, changelog, and guidance aligned with what shipped.
Confirm the published docs describe this release, or record the remaining stale pages for the next pass.
Real numbers only. No card on free. Checkout can wait — start from the dashboard.
2 loops. No card.
10 loops. The overnight default.
When more people share the loops.
When the org outgrows a small set of loops.
Pro is $19/mo for 10 loops. Wake up with notes that match what actually shipped.
Get Pro · $19/mo