releasio do-release¶
Complete release workflow in one command.
Usage¶
Description¶
The do-release command combines the entire release process:
- Updates version and changelog
- Commits the changes
- Creates and pushes a git tag
- Publishes to PyPI
Perfect for projects that don't need PR review.
Arguments¶
| Argument | Type | Default | Description |
|---|---|---|---|
PATH |
Path | . |
Project directory path |
Options¶
| Option | Description |
|---|---|
--execute |
Actually release (default: dry-run) |
--skip-publish |
Skip PyPI publishing |
--version |
Override calculated version |
--prerelease |
Create pre-release (alpha, beta, rc) |
--verbose |
Show detailed output |
Examples¶
Preview (Dry-Run)¶
Execute Full Release¶
Example Output
╭─ Full Release: my-project ───────────────────────────────╮
│ │
│ 📦 Version: 1.2.0 → 1.3.0 │
│ │
│ ✅ Updated pyproject.toml │
│ ✅ Updated CHANGELOG.md │
│ ✅ Committed: chore(release): prepare v1.3.0 │
│ ✅ Created tag v1.3.0 │
│ ✅ Pushed to origin │
│ ✅ Created GitHub release │
│ ✅ Published to PyPI │
│ │
│ 🎉 Release complete! │
│ │
╰──────────────────────────────────────────────────────────╯
Force Specific Version¶
Create Pre-Release¶
Creates version like 1.3.0-beta.1.
Skip Publishing¶
Workflow Comparison¶
| Approach | Commands | PR Review |
|---|---|---|
| Release PR | release-pr → merge → release |
Yes |
| Do Release | do-release |
No |
When to Use
Use do-release for:
- Personal projects
- CI/CD pipelines with existing review gates
- Rapid iteration phases
Use release-pr for:
- Team projects
- When changelog review is important
- When PR checks need to run
See Also¶
- release-pr - PR-based workflow
- release - Just tag and publish