Skip to content
MagmaMoosePublic

About

GitHub Action + Cloudflare Worker for release orchestration: multi-tool semantic versioning (python-semantic-release, semantic-release, GitVersion, release-please), Docker build/scan with CycloneDX SBOM to Dependency-Track, GHCR image promotion, promotion PRs, and npm/maven/gradle/rubygems publishing. GitHub Enterprise-compatible.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Use this GitHub action with your project
Add this Action to an existing workflow or create a new one
View on Marketplace

Diatreme

CI Latest release GitHub Marketplace Docs License

One GitHub Action for your whole release spine: versioning, releases, signed commits, Docker promotion, and SBOMs, on both GitHub.com and Enterprise.

Merge a conventional commit and Diatreme computes the semantic version, writes the tag, GitHub Release and changelog, promotes your already-built Docker image by provenance-verified retag, and emits a CycloneDX SBOM. The same workflow serves a mixed stack: python-semantic-release, semantic-release, GitVersion and release-please are all detected from repository markers, so a whole org shares one release job.

Documentation · Install the GitHub App · Action reference · Marketplace

Quickstart

Production-only release from main, using the hosted App token broker:

name: Release
on:
  push:
    branches: [main]

jobs:
  release:
    runs-on: ubuntu-latest
    permissions:
      contents: write     # create tags and GitHub Releases
      id-token: write     # exchanges GitHub OIDC for a short-lived installation token
    steps:
      - uses: MagmaMoose/diatreme@v2
        with:
          environment: prod
          environments: '["prod"]'
          prerelease-identifiers: '{}'

Install the Diatreme GitHub App, add your versioning tool's config, and merge conventional commits. Nothing to register, no token to rotate.

What it does

  • Versioning, your way — auto-detects python-semantic-release, semantic-release, GitVersion or release-please from repo markers, so one shared workflow serves a mixed-stack org.
  • Releases — tag, GitHub Release, changelog and normalised outputs, with App-attributed signed release commits.
  • Docker, promoted not rebuilt — build pr-N images, then promote the exact scanned artifact to the release tag by digest, verifying provenance first.
  • Supply chain built in — scan the assembled image on the PR to gate it, then route the released image's CycloneDX SBOM to Dependency-Track, with optional findings to DefectDojo. One project version per release, not one per pull request.
  • Publish anywhere — npm, NuGet, Maven, Gradle, RubyGems, containers, pip and signed Helm charts listed on Artifact Hub, to GitHub Packages or public registries.
  • Multi-environment promotion — dev → staging → prod with promotion PRs, release branches cut on demand, a signed-off RC promoted to stable by tag (never rebuilt), GitOps deploy PRs.

A wrong tag-prefix ships the wrong version, silently. In a repo releasing several packages, nothing errors: the release succeeds and the artifact publishes carrying a version computed from another package's history. See Releasing several packages.

flowchart LR
  C[Conventional commits] --> D{Diatreme}
  D -->|version| R[Tag · GitHub Release · Changelog]
  D -->|docker| I[Build pr-N → Scan → Promote by digest → Scan release → SBOM]
  D -->|packages| P[npm · NuGet · Maven · Gradle · pip · gem]
  I --> DT[(Dependency-Track)]
  I --> DD[(DefectDojo)]
Loading

Most-used inputs

Input Default What it does
mode release ci builds a PR image · release versions and promotes · cut-release-branch · enable-auto-merge.
auth-mode public-app Token source. The default uses the hosted App and needs only id-token: write.
versioning-tool auto Detected from repo markers; override to pin one.
environment — The environment this run releases to.
publish-package — Language package to publish: npm · nuget · maven · pip · …
tag-prefix — Scopes the release when one repo ships several packages.

All 110 inputs and every output → Action reference

Documentation

Setup Install the App, wire the workflow, develop locally
Using the action · Versioned suites Modes, Docker builds, image scanning, signing, publishing packages, suite release notes
Action reference Every input and output, generated from action.yml
Architecture · Broker How it works, and the hosted broker behind it
Errors · Limits What went wrong, and what it will not do

Where it sits

Diatreme releases · Tremvok deploys and verifies · Chargate gates security · Brimyr gates tests

Versioning

Pin @v2 for the floating major, or a tag or SHA to freeze.

Security · Contributing · License

Report a vulnerability · Contributing · MIT, see LICENSE.

About

GitHub Action + Cloudflare Worker for release orchestration: multi-tool semantic versioning (python-semantic-release, semantic-release, GitVersion, release-please), Docker build/scan with CycloneDX SBOM to Dependency-Track, GHCR image promotion, promotion PRs, and npm/maven/gradle/rubygems publishing. GitHub Enterprise-compatible.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Releases

Used by

Contributors

Languages