MacHu-GWU/sqlalchemy_upsert_kit-project / .claude/skills/pywf-oss-base
pywf-oss-base
FlaggedShared conventions, references, and scripts of the pywf-oss skills for pywf open-source Python libraries: setup, layout, code style, tests, user docs and the agent skills that hold API and maintenance knowledge, CI and hosting, release, dependencies, and secrets. Load it before ad-hoc work on modules, tests, or docs in such a repo, for a question about these conventions, or when unsure which pywf-oss skill fits a job.
references/23-release.md
View on GitHub---
description: "The release sequence from a finished change to PyPI and a GitHub tag and release: who does each step, the publish and release tasks, and the approval gate before each public step. Read when publishing a new version."
---
# Release
---
## 1. Sequence
| Step | Who | How |
| :--- | :--- | :--- |
| 1. Bump the version (`22-versioning-and-changelog.md`) | AI, after the user's yes on the number | edit `pyproject.toml`, then `mise run inst` |
| 2. Write that version's changelog section | AI | `22-versioning-and-changelog.md` |
| 3. Verify | AI | `mise run cov`, `mise run lint`, `mise run build-doc` all pass |
| 4. Commit and push to `main` | AI, after the user's yes | git |
| 5. Publish to PyPI | AI, after the user's yes | `mise run publish` (builds, then `uv publish` with `PYPI_TOKEN`) |
| 6. Create the GitHub tag and release | AI, after the user's yes | `mise run release` (idempotent) |
---
## 2. Rules
- **Steps 5 and 6 are irreversible and public.** One yes per step (`03-mise.md` section 3): a yes to publish is not a yes to release.
- **Never delete or move a published tag or PyPI release.** Fix a bad release with a new PATCH version.
- **A missing or rejected token** is reported by its variable name, and the release stops there (`01-secrets.md`).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |