Release Process — Owner Only
SkillDev toolsRelease checklist for type_enforced (version bump, docs regeneration, build, publish). Owner-only — do not execute; use this when asked to cut a release, bump the version, generate docs, or publish to PyPI, to explain why you're stopping instead.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Release Process — Owner Only skill
What this skill tells your AI
The instructions your AI receives, as published by connor-makowski/type_enforced in .claude/skills/release/SKILL.md and read by ahel’s review.
DO NOT RUN A RELEASE CYCLE. Do not bump the version, regenerate docs, build distributions, or publish to PyPI. These steps are owner-only. If you think a release is needed, flag it to the user and stop — don't execute any of the steps below yourself.
This includes utils/docs.py: it rebuilds type_enforced/__init__.py's
docstring from README.md, then shells out to pdoc to regenerate HTML
docs for the current version and every historical version listed in its
OLD_DOC_VERSIONS.
For reference, the full checklist (owner executes manually):
- Bump
versioninpyproject.tomlandsetup.cfg— they must match - Run
uv run python utils/prettify.py - Run
uv run nox— all sessions must pass - Run
uv run python utils/docs.pyto rebuild__init__.pyfromREADME.mdand regenerate pdoc docs - Publish with the appropriate script
Signals
- GitHub stars
- 64
- Forks
- 6
- Last commit
- Sep 2026
- Hacker News mentions
- 20
Advanced
- Catalog kind
- skill
- Gateway key
release-connor-makowski- Source
- github.com/connor-makowski/type_enforced