CONTENT CREATION

Release Notes Publish to Readme Docs and Discord

When a release is tagged, drafts versioned release notes from the diff and publishes them straight to your Readme changelog.

CategoryContent Creation
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerGitLab release tag publishedGitLabGitLab
  • ActionCollect MRs included in the tagGitLabGitLab
  • ActionDraft developer release notes with LLMOpenAI
  • ActionPublish Readme changelog entryReadMeReadMe
  • OutputAnnounce new version in DiscordDiscordDiscord

What it does

Keeps your hosted product docs and developer community in sync with each tagged release. It builds versioned release notes from the MRs in the tag, publishes them as a Readme changelog entry, and posts a release announcement to your Discord developer community channel.

When to use it

For API and developer-tooling products that maintain a public changelog on Readme and engage developers in Discord. It removes the manual step of writing the same release twice in two places.

How it works

  1. 1A GitLab release-tag event triggers the flow with the version.
  2. 2The flow collects the MRs included in the tag and their descriptions.
  3. 3An LLM step drafts developer-oriented release notes with code-relevant detail.
  4. 4The notes are published as a new Readme changelog entry for that version.
  5. 5A formatted announcement with the changelog link is posted to Discord.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitLabRepos, MRs, pipelines, registry.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect ReadMeAPI docs, changelog, auth.
  4. 4
    Connect DiscordCommunity channels + voice + bots.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.