- AI-Agent
- Ready to Run
Publish Software Changelog
Verify shipped changes and publish a versioned changelog
Use this Agent instantly or customize it - no programming needed
- Change-note approvalChange-note approval
Your release editor approves the note pull request for a shipped version.
- Contributed change notesContributed change notes
Your approved note files describe changes and link to the work behind them.
- Release tagsRelease tags
Your note pull request names the shipped tag and the previous tag.
- Shipped code changesShipped code changes
Your commits, changed files, and linked pull requests show what shipped between the tags.
- Documentation publishing detailsDocumentation publishing details
Your chosen page path, index path, and public site URL guide publication.
Your release repository holds the approved notes, release tags, and documentation pages for each version.
- Editor issue commentEditor issue comment
Your release editor gets a pull request comment naming the gap, conflict, or error to resolve.
- Editor issue commentEditor issue comment
Your release editor gets a pull request comment naming the gap, conflict, or error to resolve.
- Editor issue commentEditor issue comment
Your release editor gets a pull request comment naming the gap, conflict, or error to resolve.
- Versioned changelog pageVersioned changelog page
Your versioned documentation page groups verified features, fixes, and breaking changes.
- Changelog index entryChangelog index entry
Your documentation index points readers to the version's changelog page.
- Editor issue commentEditor issue comment
Your release editor gets a pull request comment naming the gap, conflict, or error to resolve.
- Public changelog linkPublic changelog link
Your release editor gets the live changelog link in a comment on the note pull request.
This Agent waits for your release editor to approve change notes. It checks them against release tags, publishes a versioned changelog, and replies with its public link.
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.
AsanaUsed as:
- Release repository
Asana holds the approved notes, release tags, and documentation pages for each version.
PodioUsed as:
- Release repository
Podio holds the approved notes, release tags, and documentation pages for each version.
Made for your industry
Publish Software Changelog is made for businesses in these industries.
- Software
Publish verified changelogs for shipped software versions.
Show all Agents for the Software industry
Made for your role
Publish Software Changelog is made for people in these roles.
- Editor
Check approved change notes against what shipped before publishing.
Show all Agents for the Editor role - Release Manager
Publish a changelog that matches the tagged release.
Show all Agents for the Release Manager role - Technical Writer
Turn verified release notes into a versioned documentation page.
Show all Agents for the Technical Writer role - Release Coordinator
Carry approved release notes through changelog publication.
Show all Agents for the Release Coordinator role
Made for your department
Publish Software Changelog is made for people in these departments.
- Release Management
Check shipped changes before publishing the release changelog.
Show all Agents for the Release Management department - Documentation
Add verified version changes to the public documentation site.
Show all Agents for the Documentation department
How Publish Software Changelog works
4 steps, in order, on every run.
-
Read the approved notesConfirm the release editor approved the current change-note pull request. Read its note files and the release tags named in its description.
-
Check claims against shipped workCompare the release tags and inspect linked changes. Flag unsupported claims for the editor to resolve before publication.
-
Write the versioned changelogCorrect supported wording and group verified changes as features, fixes, or breaking changes. Link entries to the work behind them.
-
Publish the page and share its linkMerge the note pull request and add the versioned page to your documentation index. Confirm the site build succeeds, then comment with the public link.
How to Get Started
Connect the tools you already use, such as Asana or Podio.
2 tools
- Choose the release repository, the release editor's account, and the branch and folder that publish the documentation site.
- Use one change-note pull request per version. Put the shipped tag and previous tag in its description, and require each contributed note to link to the change it describes.
- Choose the versioned changelog page path, changelog index path, and public documentation URL.
Use safe mode to approve every result before it goes out, or let the Agent run automatically.
FAQs
Frequently asked questions about the Publish Software Changelog:
You choose the release repository and documentation source. You also set the changelog paths and public site URL.
No. The Agent flags unsupported claims on the pull request. Your release editor resolves them before publication.
The Agent compares the existing page with the approved notes and avoids a duplicate. Your release editor reviews any conflicting content.
No. The Agent comments with the build error on the pull request and withholds the public link.
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 Software Changelog
More ready-to-run Agents for connected work.
Your reviewers can decide on the intended creative file. The Agent flags outdated versions and asks the owner for the current one.
5 toolsYour reviewer gets the current image or PDF and a clear question. Your review card shows which revision you sent.
19 toolsYour review card shows the current proof revision and its file link, so makers and reviewers know which version needs attention.
9 toolsYour reviewer sees the current image or PDF proof link and revision on the task before deciding.
7 tools