release-publish

Automate tag-driven Docker image publication by triggering a GitHub Actions workflow upon pushing a vX.Y.Z tag. This process builds and publishes multi-arch images to GHCR while generating corresponding GitHub releases automatically.

A tag-triggered release workflow handles multi-arch Docker builds by automatically compiling images for linux/amd64 and linux/arm64. It validates version bumps and changelog alignment before publishing the finalized artifacts to GHCR.

Yes, you can enforce changelog alignment and version bumps as preconditions within your GitHub workflow. The pipeline validates these governance checks before proceeding with the Docker build and GitHub release publication.

The best way to generate release notes automatically is by using a tag-triggered workflow that parses your changelog. This mechanism extracts release notes during the tag-push event and attaches them to the newly created GitHub Release.

Yes, this tag-based publish workflow fully supports both linux/amd64 and linux/arm64 architectures. It executes multi-arch builds concurrently and pushes the resulting manifest lists directly to the GitHub Container Registry.

Your Docker publish workflow may fail when pushing a version tag if preconditions are unmet. The pipeline enforces strict version bump verification and changelog alignment checks before allowing any build or release publication to proceed.