skills.rest
awebai
awebaiOFFICIAL
Explore all skills by this author →
GitHub

release

Test and publish aweb OSS release candidates using artifact tags.

82|9|Updated Feb 2, 2026
Search Tags:#publishing#release#git tags#make#artifact#oss#ci cd
One-click install
npx skills add https://github.com/awebai/aweb --skill release-awebai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/awebai/aweb/tree/main/.claude/skills/release
Command: npx skills add https://github.com/awebai/aweb --skill release-awebai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Releasing an open-source project involves running full test suites, creating version tags, and publishing artifacts, and doing these steps manually risks shipping untested code or mismatched tags. This Skill enforces a strict release workflow where tags are only created after every test passes. ## Core Features & Use Cases - Gated Release Candidates: Runs make release-candidate to execute all local Docker tests and E2E suites, creating artifact tags only on complete success. - Per-Tag Publishing: Pushes each tag individually so each one triggers only its own thin artifact publisher without rerunning product suites. - Outage Fallback: Provides make release-publish with registry credentials for publishing during hosted-runner outages. - Use Case: A maintainer finalizes a clean commit on main, decides the version tags, and uses this Skill to test, tag, and publish the release in the correct order. ## Quick Start Run the release skill to test and publish version v1.2.0 of the aweb OSS project from the current clean commit.

Frequently Asked Questions about release

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

FAQPage Schema
How do I publish an aweb OSS release?▼

Run `make release-candidate TAGS='tag-vX.Y.Z ...'` from the final clean commit, then push each resulting tag with `git push origin refs/tags/<tag>`. Each tag triggers only its own artifact publisher.

How do I create release tags only after tests pass?▼

Use the release-candidate make target, which runs every local Docker test and E2E suite first. Tags are created only when the full test run completes successfully, preventing untested code from being tagged.

What happens when I push a release tag?▼

Each pushed tag invokes only its thin artifact publisher for that specific artifact. Hosted publishers never rerun the product test suites, keeping the publish step fast and isolated.

How do I publish a release during a CI runner outage?▼

Use `make release-publish TAG=<tag>` with the registry credential documented in docs/release.md. This bypasses the hosted runners so the artifact can still be published manually.

Can I create release tags before running the test suite?▼

No. The workflow requires deciding artifact tags upfront but creating them only through the release-candidate target, which gates tag creation on complete test success from a clean commit.

Related Skills

Explore More Software Engineering Skills→
mistakenotmistakenot

complete-task

Finalizes a feature branch and merges its pull request to main.

Community
Intermediate
jordanfbrownjordanfbrown

nexus-publishing

Publish front-end monorepo packages to a Nexus registry with version bumps and changelog updates.

Community
Advanced
SimplexLabSimplexLab
392

prepare-release

Verify changelog, README, and version in pyproject.toml for TorchJD releases.

Official
Advanced
ruifrvazruifrvaz
3

smaqit.release-approval

Validate release version approval via pattern matching or user confirmation.

Community
Intermediate