How do I install the Aiogram Release skill?

Run npx skillmds@latest add aiogram/aiogram-release in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Aiogram Release safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Aiogram Release?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Aiogram Release free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Aiogram Release?

aiogram (@aiogram) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Aiogram Release by aiogram — Agent Skill

Name: Aiogram Release
Author: aiogram

Aiogram Release

Cut an aiogram release — bump the version, build the changelog from the CHANGES fragments, verify the version-carrying files, tag. Use when asked to "prepare a release", "bump the version", "build the changelog", or "release 3.x.y".

aiogram 81d1d42 2.6 KB Updated Sep 17, 2026

File contents

Prepare a release

Recurring maintainer chore — aiogram/__meta__.py and CHANGES.rst have each been touched ~46 times in the last 300 commits, always in the same shape: Bump version → Bump changelog → Release X.Y.Z + tag.

Maintainer-only, and it writes to the working tree. Confirm the target version with the user before running anything, and never push or tag without being asked.

1. Preview the notes

rtk proxy make towncrier-draft            # rtk proxy uv run --extra docs towncrier build --draft

Every fragment in CHANGES/ shows up here. Fix wording in the fragment files, not in the draft. Categories: feature, bugfix, doc, removal, misc.

2. Bump

rtk proxy make bump args=patch            # or minor | major | to:3.31.0

Runs both scripts:

scripts/bump_version.py <part> → aiogram/__meta__.py::__version__
scripts/bump_versions.py → reads .butcher/schema/schema.json api.version, writes .apiversion, __meta__.py::__api_version__, the API-<ver>-blue.svg badge and the "Supports Telegram Bot API …" line in README.rst, and the badge in docs/index.rst

Verify all five landed:

rtk git diff --stat -- aiogram/__meta__.py .apiversion README.rst docs/index.rst

3. Build the changelog

rtk proxy make towncrier-build            # towncrier build --yes: consumes CHANGES/*.rst into CHANGES.rst

rtk proxy make prepare-release = step 2 + step 3 in one go. This is the only sanctioned way CHANGES.rst gets edited.

4. Sanity

rtk proxy uv run python -c 'from aiogram import __version__, __api_version__; print(__version__, __api_version__)'
rtk git status --short               # CHANGES/ fragments must now be deleted, CHANGES.rst grown
rtk test uv run pytest tests -q
rtk proxy uv build

5. Tag (only on explicit request)

rtk proxy make release                     # git add . && commit "Release X.Y.Z" && git tag vX.Y.Z

Publishing runs from .github/workflows/pypi-release.yml on the tag — do not uv publish by hand.

Known wart

scripts/bump_versions.py::get_package_version() still reads pyproject.toml → tool.poetry.version, which no longer exists since the move to hatchling/uv. It is dead code (main() never calls it), so the bump works — but do not reuse that function.

---name: aiogram-releasedescription: Cut an aiogram release — bump the version, build the changelog from the CHANGES fragments, verify the version-carrying files, tag. Use when asked to "prepare a release", "bump the version", "build the changelog", or "release 3.x.y".---# Prepare a releaseRecurring maintainer chore — `aiogram/__meta__.py` and `CHANGES.rst` have each beentouched ~46 times in the last 300 commits, always in the same shape:`Bump version` → `Bump changelog` → `Release X.Y.Z` + tag.Maintainer-only, and it writes to the working tree. Confirm the target version withthe user before running anything, and never push or tag without being asked.## 1. Preview the notes```bashrtk proxy make towncrier-draft # rtk proxy uv run --extra docs towncrier build --draft```Every fragment in `CHANGES/` shows up here. Fix wording in the fragment files, not inthe draft. Categories: `feature`, `bugfix`, `doc`, `removal`, `misc`.## 2. Bump```bashrtk proxy make bump args=patch # or minor | major | to:3.31.0```Runs both scripts:- `scripts/bump_version.py <part>` → `aiogram/__meta__.py::__version__`- `scripts/bump_versions.py` → reads `.butcher/schema/schema.json` `api.version`, writes `.apiversion`, `__meta__.py::__api_version__`, the `API-<ver>-blue.svg` badge and the "Supports `Telegram Bot API …`" line in `README.rst`, and the badge in `docs/index.rst`Verify all five landed:```bashrtk git diff --stat -- aiogram/__meta__.py .apiversion README.rst docs/index.rst```## 3. Build the changelog```bashrtk proxy make towncrier-build # towncrier build --yes: consumes CHANGES/*.rst into CHANGES.rst````rtk proxy make prepare-release` = step 2 + step 3 in one go. This is the only sanctioned way`CHANGES.rst` gets edited.## 4. Sanity```bashrtk proxy uv run python -c 'from aiogram import __version__, __api_version__; print(__version__, __api_version__)'rtk git status --short # CHANGES/ fragments must now be deleted, CHANGES.rst grownrtk test uv run pytest tests -qrtk proxy uv build```## 5. Tag (only on explicit request)```bashrtk proxy make release # git add . && commit "Release X.Y.Z" && git tag vX.Y.Z```Publishing runs from `.github/workflows/pypi-release.yml` on the tag — do not`uv publish` by hand.## Known wart`scripts/bump_versions.py::get_package_version()` still reads`pyproject.toml → tool.poetry.version`, which no longer exists since the move tohatchling/uv. It is dead code (`main()` never calls it), so the bump works — but do notreuse that function.

Frequently asked questions