- AI-Agent
- Ready to Run
Publish Release Changelog
Turn GitHub commits into release notes for new tags
Use this Agent instantly or customize it - no programming needed
- New release tagNew release tag
Your new tag identifies the repository, version, and tagged commit.
- Published release historyPublished release history
Your earlier releases identify the previous tag in the same release line.
- Release for the new tagRelease for the new tag
Your new tag may already have a release page to share.
- Compared commitsCompared commits
Your commit messages and links show what changed since the previous release.
- Release note preferencesRelease note preferences
Your chosen headings, style, and unclear-commit rule guide the notes.
Your release platform supplies tags, release history, and commits, then hosts the published notes.
- Release page linkRelease page link
You get a link to the new or existing release page.
- Starting tag requestStarting tag request
You choose the starting tag when no earlier release matches your release line.
- Comparison issueComparison issue
You get the tag and reason when the commit comparison has no usable result.
- Published release notesPublished release notes
Your release page shows supported changes under Features, Fixes, and Other Changes.
- Release page linkRelease page link
You get a link to the new or existing release page.
This Agent starts when you push a release tag. It checks for an existing release and finds the prior tag. It compares commits and publishes a categorized changelog as release notes.
Modify Agent
Customize this Agent to fit your needs using natural language.
Start Agent for Free
Enter your email address and we will send you a secure link to continue.
monday.comUsed as:
- Release platform
monday.com supplies tags, release history, and commits, then hosts the published notes.
AsanaUsed as:
- Release platform
Asana supplies tags, release history, and commits, then hosts the published notes.
GitHubUsed as:
- Release platform
GitHub supplies tags, release history, and commits, then hosts the published notes.
Made for your industry
Publish Release Changelog is made for businesses in these industries.
- Software
Publish clear release notes for each tagged software version.
Show all Agents for the Software industry
Made for your role
Publish Release Changelog is made for people in these roles.
- Software Delivery Manager
Document changes as each tagged version goes out.
Show all Agents for the Software Delivery Manager role - Release Manager
Publish categorized notes for each newly tagged release.
Show all Agents for the Release Manager role - Software Engineer
Turn commit history into readable notes for a new version.
Show all Agents for the Software Engineer role - DevOps Engineer
Publish release notes when a version tag is pushed.
Show all Agents for the DevOps Engineer role
Made for your department
Publish Release Changelog is made for people in these departments.
- Software Engineering
Summarize code changes on each tagged release page.
Show all Agents for the Software Engineering department - Release Management
Keep published release notes in step with new version tags.
Show all Agents for the Release Management department - DevOps
Create release pages with notes after new tags are pushed.
Show all Agents for the DevOps department
How Publish Release Changelog works
4 steps, in order, on every run.
-
Check Release HistoryCheck whether the new tag already has a release and find the prior tag. Leave an existing release unchanged and report its link.
-
Compare Tagged CommitsCompare the new tag with the prior release tag. Read every returned commit, including later pages.
-
Draft the ChangelogGroup supported changes under Features, Fixes, and Other Changes. Describe unclear commits cautiously and link to them.
-
Publish Release NotesCreate a published release with the changelog as its body. Return the release page link.
How to Get Started
Connect the tools you already use, such as monday.com, Asana or GitHub.
3 tools
- Choose the repository, release-tag pattern, and how to identify the previous published release in the same release line.
- Set the headings and writing style for the release notes, including how to describe commits that are unclear.
- Connect a tag-push webhook and grant access to read commits and releases and create published releases.
Use safe mode to approve every result before it goes out, or let the Agent run automatically.
FAQs
Frequently asked questions about the Publish Release Changelog:
Yes. Choose the repository, release-tag pattern, and how to identify the previous release in the same release line.
The maintainer chooses a starting tag when no prior release matches your setup. The Agent stops until then.
The existing release stays unchanged, and you get its link. The Agent does not replace those notes.
Unclear commits go under Other Changes with cautious wording and links. If the comparison is empty or fails, you get the reason and no new release notes.
It stops and asks you. The Agent does not guess when it reaches a decision you have not approved.
Yes. Every run creates a plain-language log that you can review and export. Logs are kept for twelve months.
The Agent stops at the end of the billing month and its tool connections are removed. Your run logs remain available for twelve months.
Agents related to Publish Release Changelog
More ready-to-run Agents for connected work.
Your reviewer gets the current image or PDF and a clear question. Your review card shows which revision you sent.
19 toolsYour coordinator gets both revision links in chat when the task and current proof differ, with the task held for a human choice.
17 toolsYour review card shows the current proof revision and its file link, so makers and reviewers know which version needs attention.
9 toolsYour rework card points to the latest image or PDF proof, with the next reviewer clear when a shared file changes.
9 tools