Why
The AI release-notes category lives on the GitHub Marketplace — github/copilot-release-notes, AbsaOSS/generate-release-notes, combinatrix-ai/release-note-writer, and the various ai-release-notes-action entries all ship that way.
docs/ci-cd.md explains how to wire the CLI into Actions, but there is no Marketplace listing. Anyone searching "release notes action" never finds this project.
Scope
action.yml at the repository root, composite or Node-based.
- Inputs:
from, to, env, provider, format, language, config-path, api-key.
- Outputs: generated markdown, the paths written, and token usage, so downstream steps can post to a release or a PR comment.
- A tagged major ref (
v1) that moves, per Marketplace convention.
- Example workflows in
docs/ci-cd.md: on tag push, and on release publish.
Acceptance criteria
Files
New action.yml, docs/ci-cd.md, .github/workflows/
Depends on
Worth doing after the quality issues land — a Marketplace listing is a first impression, and it should be made with the better output.
Why
The AI release-notes category lives on the GitHub Marketplace —
github/copilot-release-notes,AbsaOSS/generate-release-notes,combinatrix-ai/release-note-writer, and the variousai-release-notes-actionentries all ship that way.docs/ci-cd.mdexplains how to wire the CLI into Actions, but there is no Marketplace listing. Anyone searching "release notes action" never finds this project.Scope
action.ymlat the repository root, composite or Node-based.from,to,env,provider,format,language,config-path,api-key.v1) that moves, per Marketplace convention.docs/ci-cd.md: on tag push, and on release publish.Acceptance criteria
action.ymlvalidates and runs from a clean checkoutv1moving tagFiles
New
action.yml,docs/ci-cd.md,.github/workflows/Depends on
Worth doing after the quality issues land — a Marketplace listing is a first impression, and it should be made with the better output.