release · v1.0.0 · 2026-03-21 · sha256 a4f5b7ae9e50732d
release v1.0.0A
Immutable. This exact content is served forever at /api/v1/blob/a4f5b7ae9e50732d.
---
name: release
description: Release preparation and publishing
category: primary
aliases: [rel, ship]
tags: [release, publish, version, changelog]
version: "1.0.0"
question:
header: "Release"
question: "What release task do you need?"
multiSelect: false
options:
- label: "Prep check"
description: "Run release readiness checks"
- label: "Security pre-check"
description: "Security audit before release"
- label: "Health check"
description: "Code health and quality check"
- label: "Publish"
description: "Bump version and publish"
---
# release
Release preparation, validation, and publishing.
## Routes
| Subcommand | Action |
| ---------- | ------ |
| `prep` | Release readiness checks |
| `security` | Pre-release security audit |
| `health` | Code health check |
| `publish` | Version bump and publish |
## Usage
```bash
/release # Ask what to do
/release prep # Release prep checks
/release security # Security audit
/release health # Health check
/release publish # Publish release
```
## Behavior
### prep
Run release preparation workflow:
```bash
uv run attune workflow run release-prep
```
This checks:
- Test suite passes
- No critical security issues
- Documentation is current
- Changelog is updated
### security
Run security audit focused on release readiness:
```bash
uv run attune workflow run security-audit --path src/
```
### health
Run code health checks:
- Test coverage
- Lint status
- Type check status
- Dependency audit
### publish
Use `AskUserQuestion` to confirm:
- Version bump type? (patch, minor, major)
- Changelog reviewed?
- All checks passing?
Then guide through:
1. Version bump in pyproject.toml
2. Update CHANGELOG.md
3. Create git tag
4. Push and publish