DEVOPS

Localized release notes from a GitHub tag

When a new version tag is pushed to GitHub, generate clean release notes from the merged PRs, translate them into your target languages.

CategoryDevOps
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew version tag pushed (v*)GitHubGitHub
  • ActionFetch merged PRs since previous tagGitHubGitHub
  • ActionDraft grouped English release notesHugging FaceHugging Face
  • ActionTranslate notes into target localesHugging FaceHugging Face
  • OutputPublish multilingual GitHub ReleaseGitHubGitHub

What it does

Turns a freshly pushed Git tag into polished, multilingual release notes. It reads the PRs merged since the previous tag, drafts human-readable notes, translates them into the languages you ship in, and attaches every translation to the GitHub Release.

When to use it

Use it when your repo serves a global user base and you want every release to land with native-language notes the moment you cut a tag — without a manual copy-paste-translate ritual each time.

How it works

  1. 1A new tag matching `v*` is pushed to the repository (trigger).
  2. 2The flow diffs the new tag against the previous one and pulls the list of merged PR titles, bodies, and labels from GitHub.
  3. 3An LLM groups changes into Features / Fixes / Breaking and writes concise English notes.
  4. 4A translation step calls a Hugging Face multilingual model to produce one note set per target locale.
  5. 5The flow assembles a single Release body with collapsible per-language sections and publishes it to the GitHub Release for that tag.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitHubRepos, issues, pull requests, actions.
  2. 2
    Connect Hugging FaceModels, datasets, spaces — the open-source hub.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.