Release

Name: Release
Author: awebai

ASecurity

Test and publish one exact aweb OSS candidate using artifact tags.

110 stars
0 votes
0 copies
1 view
Added September 25, 2026

ai-agentsdockertestinggit

Security analysis

A100/100

Scanned September 25, 2026

npx -y skills add awebai/aweb --skill release --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Release?

Add the live security badge to your README. It updates with every re-scan.

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/awebai-release/badge)](https://www.skillsdirectory.com/skills/awebai-release)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: release
description: Test and publish one exact aweb OSS candidate using artifact tags.
---

# Release OSS

`main` is synchronization only. Decide the artifact tags before testing.

1. Run `make release-candidate TAGS='tag-vX.Y.Z ...'` from the final clean
   commit. It runs every local Docker test and E2E and creates the tags only on
   complete success.
2. Push each resulting tag separately with `git push origin refs/tags/<tag>`.
3. Each tag invokes only its thin artifact publisher; hosted publishers never
   rerun product suites.

During a hosted-runner outage, use `make release-publish TAG=<tag>` with the
registry credential documented in `docs/release.md`.