One changelog
per release.
Connect a GitLab project, hit sync. Drumroll lists every GitLab Release and turns each one into a changelog entry - title, description, release date, all preserved. Refresh tokens rotate transparently so the connection just stays connected.
How it works
Three steps,
under five minutes.
- 01
Authorize GitLab
Standard OAuth 2.0 flow on gitlab.com. Scopes: read_api, read_repository. Tokens are AES-256 encrypted before they touch our database and refreshed automatically when they expire.
- 02
Pick a project
Type the project path as group/repo (or group/subgroup/repo for nested namespaces). Drumroll resolves it to the numeric project ID and stores both so future syncs are fast.
- 03
Sync on demand
Click Sync now. Each GitLab Release becomes one changelog entry. Upcoming releases (with a future date) come in as drafts. Re-syncs update entries in place using tag_name as the stable ref - no duplicates.
What syncs
Capabilities & limits.
We’re explicit about what GitLab sync handles and what it doesn’t. Most teams find the first list covers their actual use; the second is the part vendors usually hide.
Supported
- GitLab OAuth with read_api + read_repository scopes
- Refresh tokens rotated transparently every ~2 hours
- Release description rendered as markdown (links, code, lists)
- Stable source-ref dedupe via project_path + tag_name
- Upcoming releases (future released_at) come in as drafts
- Nested namespaces supported (group/subgroup/repo)
Not yet supported
- Self-managed GitLab instances - gitlab.com only for v1
- Webhook-driven sync - on-demand by design
- Issue / MR sync - releases only
- Reading GitLab CI artifacts or job logs
Try it on a real project.
Two minutes to sign up, one click to connect, your team’s shipping rhythm becomes a public page. Always free.
Create a workspace