release

Coordinate GitHub Actions workflows for continuous deployment and versioned releases.

11|4|Updated Jan 15, 2024
One-click install
npx skills add https://github.com/Systemorph/MeshWeaver --skill release-systemorph
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/Systemorph/MeshWeaver/tree/main/.claude/skills/release
Command: npx skills add https://github.com/Systemorph/MeshWeaver --skill release-systemorph

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the manual complexity and risk associated with shipping software, ensuring consistent, versioned, and secure releases across continuous and official channels.

Core Features & Use Cases

  • Dual-Channel Pipeline: Manages both continuous integration builds and official versioned releases with distinct workflows.
  • Automated Deployment: Orchestrates multi-arch Docker image creation, NuGet package publishing, and cluster rollouts.
  • Use Case: When ready to ship a new version, use this skill to safely tag the repository, trigger the official release pipeline, and verify the health of the automated deployment across your infrastructure.

Quick Start

Use the release skill to verify the current CI status and tag the repository with the next version number to trigger the official release pipeline.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate Kubernetes deployment and NuGet package publishing in a CI-CD pipeline?

Automating Kubernetes deployment and NuGet publishing requires coordinating GitHub Actions workflows to build multi-arch Docker images, push packages, and trigger automated cluster rollouts. This skill manages that end-to-end release lifecycle using tag-driven triggers and pre-deployment validation.

What is the best way to manage continuous deployment and official versioned releases separately?

Managing continuous deployment and official versioned releases separately requires a dual-channel pipeline. This skill coordinates distinct GitHub Actions workflows for continuous integration builds and official versioned releases, ensuring consistent and secure shipping across both channels.

Does GitHub Actions work with multi-arch Docker image generation and Kubernetes cluster updates?

Yes, GitHub Actions works for multi-arch Docker image generation and Kubernetes cluster updates. This skill orchestrates these actions together, facilitating automated cluster rollouts and ensuring release integrity through tag-driven triggers and pre-deployment validation checks.

How do I trigger an official release pipeline and verify deployment health for MeshWeaver?

Triggering an official release pipeline involves verifying the current CI status and tagging the repository with the next version number. This action initiates the official release workflow, which orchestrates Docker image creation, NuGet publishing, and automated Kubernetes cluster updates.

Why does tagging a repository trigger an automated deployment workflow?

Tagging a repository triggers an automated deployment workflow because the release process uses tag-driven triggers to ensure release integrity. This mechanism coordinates the GitHub Actions workflows necessary for building multi-arch Docker images and updating Kubernetes clusters.

Can I use this release automation skill without pre-deployment validation checks?

Using release automation without pre-deployment validation checks is not recommended because this skill ensures release integrity through these checks. They are a core part of the end-to-end release lifecycle before orchestrating multi-arch Docker image generation and Kubernetes cluster rollouts.