skills.rest
carrotwaxr
carrotwaxrCOMMUNITY
Explore all skills by this author →
GitHub

release-workflow

Automate release preparation and Docker image publishing for peek-stash-browser.

37|6|Updated Oct 10, 2025
Search Tags:#automation#ci/cd#versioning#release#docker#github-actions#tagging
One-click install
npx skills add https://github.com/carrotwaxr/peek-stash-browser --skill release-workflow-carrotwaxr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-workflow
Source: https://github.com/carrotwaxr/peek-stash-browser/tree/main/.claude/skills/release-workflow
Command: npx skills add https://github.com/carrotwaxr/peek-stash-browser --skill release-workflow-carrotwaxr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes manual, error-prone steps from preparing and executing releases for peek-stash-browser by consolidating validation, versioning, tagging, and Docker image publishing into a repeatable workflow.

Core Features & Use Cases

  • Pre-release validation: Run server and client unit tests, linters, integration tests, client build, and a production Docker build to ensure release readiness.
  • Version management and tagging: Automate synchronized version bumps in client/package.json and server/package.json, commit changes, create semver or beta tags, and push to origin.
  • CI/CD publication: Trigger GitHub Actions on tags to build multi-arch Docker images, apply semver and channel tags (latest, stable, beta), and publish to Docker Hub.

Quick Start

Run the release-workflow to validate tests, bump synchronized versions, tag the release, and push to trigger GitHub Actions and Docker Hub publication.

Frequently Asked Questions about release-workflow

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

FAQPage Schema
How do I automate Docker image publishing and version bumping in a CI/CD release workflow?▼

Automating Docker image publishing and version bumping involves validating tests, synchronizing version numbers across packages, creating git tags, and triggering CI/CD pipelines to build and push multi-arch images.

What is the best way to synchronize client and server package.json versions before a release?▼

Synchronizing client and server package.json versions requires an automated version bumping process that updates both files simultaneously, commits the changes, and tags the release before pushing to the remote repository.

How do I trigger GitHub Actions to build multi-arch Docker images with semver and channel tags?▼

Triggering GitHub Actions to build multi-arch Docker images is done by pushing a git tag to the main branch, which initiates a workflow to build amd64 and arm64 images and apply semver and channel tags like latest or beta.

Can I validate unit and integration tests before tagging a release in GitHub Actions?▼

Validating unit and integration tests before tagging a release ensures release readiness by running server and client test suites, linters, and a production Docker build prior to committing version changes and creating tags.

Does this release workflow support both amd64 and arm64 Docker Hub publications?▼

Supporting both amd64 and arm64 Docker Hub publications is a core feature, building production Docker images for both architectures and pushing semver and channel tags to the registry upon a successful release trigger.

Why do I need to run linters and a production Docker build during pre-release validation?▼

Running linters and a production Docker build during pre-release validation catches code quality issues and build failures early, ensuring that only stable, correctly packaged code is tagged and published to Docker Hub.

Related Skills

Explore More Software Engineering Skills→
carrotwaxrcarrotwaxr
37

release-stable

Bump client and server package.json versions and push a matching git tag.

Community
Advanced
apetteyapettey

GitHub CI/CD for Snoop Docker Images

Automate Docker image builds and pushes for backend and frontend services using GitHub Actions and Docker Buildx.

Community
Advanced
NoobyGainsNoobyGains
78

quality-enforcement

Enforce code quality standards across pre-commit, pre-merge, and CI pipeline stages.

Community
Advanced
vanman2024vanman2024
3

Version Management

Apply semantic versioning, generate changelogs from commits, and create release tags.

Community
Basic