Skip to content

release-workflows

release-artifacts.yml orchestrates tag-driven publication and calls release-github.yml, release-pypi.yml, and release-ghcr.yml as reusable workflow surfaces.

The split keeps each publication surface explicit:

  • release-pypi.yml governs PyPI publication behavior
  • release-ghcr.yml governs GHCR bundle publication behavior
  • release-github.yml governs GitHub Release publication behavior
  • release-artifacts.yml orchestrates build + publish order for tag-driven releases

Workflow Anchors

  • .github/workflows/release-artifacts.yml
  • .github/workflows/release-github.yml
  • .github/workflows/release-pypi.yml
  • .github/workflows/release-ghcr.yml
  • package release metadata and staged release assets

Current Job Tree

  • release-artifacts.yml: build matrix + reusable release workflow orchestration
  • release-pypi.yml: resolve + publication jobs for configured package inputs
  • release-ghcr.yml: resolve + per-package GHCR artifact publication
  • release-github.yml: release planning + GitHub Release publication

Purpose

Use this page to understand which release surfaces are published and how the tag-driven workflow split is organized.

Stability

Keep it aligned with the three release workflows and their shared artifact and release configuration contracts.