release-publish

Name: release-publish
Availability: InStock
Author: cyanautomation

Automate tag-triggered Docker image and GitHub release publication.

1|Updated Jan 14, 2026

Search Tags:#automation #versioning #github #docker #release-management #ci-cd #ghcr

Ready to run

npx skills add https://github.com/CyanAutomation/motioninocean --skill release-publish

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release-publish
Source: https://github.com/CyanAutomation/motioninocean/tree/main/.github/skills/release-publish
Command: npx skills add https://github.com/CyanAutomation/motioninocean --skill release-publish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the tag-triggered publication flow for Docker images and GitHub releases, ensuring consistent release artifacts and reducing manual steps.

Core Features & Use Cases

Tag-based release triggers: automatically starts the publish workflow when a tag matching vX.Y.Z is pushed.
Multi-arch release and notes extraction: builds and publishes images for linux/amd64 and linux/arm64, and generates release notes for GitHub.
Verification and governance: enforces preconditions (version bumps, changelog alignment) and validates release artifacts before publishing.

Quick Start

Tag a new release as vX.Y.Z to trigger the publish workflow and verify the resulting GitHub release and GHCR tags.

Frequently Asked Questions about release-publish

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate tag-driven Docker image publication to GHCR?▼

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.

How does a tag-triggered release workflow handle multi-arch Docker builds?▼

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.

Can I enforce changelog alignment and version bumps before publishing a GitHub release?▼

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.

What is the best way to generate release notes for GitHub Releases automatically?▼

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.

Does this tag-based publish workflow support both linux/amd64 and linux/arm64 architectures?▼

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.

Why does my Docker publish workflow fail when I push a new version tag?▼

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.