Release notes that write themselves
Every merge, every tag, every release — ShipLog generates polished release notes automatically. Zero manual effort.
Free for public repos · Works with any commit style
Fits your existing workflow
No changes to how you code. ShipLog sits at the end of your pipeline.
Save hours every sprint
AI generates them instantly on every release
Every commit and PR is accounted for — nothing missed
For teams shipping bi-weekly releases
Automation features
Auto-Trigger on Release
Generate notes automatically when you publish a GitHub release or push a tag.
AI Categorization
Commits sorted into Added, Fixed, Improved, and Removed automatically.
Review Before Publishing
Notes appear as drafts. Edit and publish when ready, or enable auto-publish.
REST API
Trigger generation from any CI/CD pipeline via API. GitHub Actions template included.
Subscriber Notifications
Email your users automatically when new release notes are published.
Markdown Export
Export release notes as Markdown for your GitHub releases, docs, or README.
Works with GitHub Actions
Add one step to your workflow. Done.
# .github/workflows/release.yml
name: Release
on:
release:
types: [published]
jobs:
changelog:
runs-on: ubuntu-latest
steps:
- name: Generate Release Notes
run: |
curl -X POST https://shiplog.deependventures.com/api/releases \
-H "Authorization: Bearer ${{ secrets.SHIPLOG_API_KEY }}" \
-H "Content-Type: application/json" \
-d '{"repo": "${{ github.repository }}", "tag": "${{ github.ref_name }}"}'Get Release Automation Tips
CI/CD best practices, release note templates, and developer productivity insights.
No spam. Unsubscribe anytime.
Frequently Asked Questions
How do automated release notes work?
ShipLog watches your GitHub repo for new releases, tags, or merges to main. When triggered, our AI analyzes the commits since the last release and generates categorized, human-readable notes automatically.
Can I integrate with my CI/CD pipeline?
Yes. ShipLog provides a REST API and GitHub App webhooks. Trigger changelog generation from GitHub Actions, CircleCI, GitLab CI, or any pipeline that can make HTTP requests.
What triggers release note generation?
Three triggers: (1) New GitHub release published, (2) New git tag pushed, (3) Manual trigger via dashboard or API. You choose which works for your workflow.
Can I review notes before publishing?
Absolutely. By default, generated notes land in your dashboard as drafts. Review, edit, and publish when ready. Or enable auto-publish for fully hands-free operation.
Do I need to change my commit message format?
No. ShipLog AI works with any commit style. That said, Conventional Commits (feat:, fix:, etc.) give the AI more signal and produce better results.
How much time does this actually save?
Teams report saving 30-60 minutes per release. For bi-weekly releases, that's 26-52 hours per year — over a full work week saved annually.
More Free Tools from ShipLog
Stop writing release notes by hand
Set up automated release notes in 5 minutes. Free for public repos.
Get Started — It's Free