python-release

Manages Python SDK release builds, dependency pin bumps, and publish verification.

30.0k|4.8k|Updated Feb 23, 2024

Search Tags:#uv #packaging #release #Python #BUILD #pyPI #dependency-pin

One-click install

npx skills add https://github.com/ComposioHQ/composio --skill python-release

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: python-release
Source: https://github.com/ComposioHQ/composio/tree/main/.agents/skills/python-release
Command: npx skills add https://github.com/ComposioHQ/composio --skill python-release

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Releasing a Python SDK involves coordinated changes across packaging metadata, dependency pins, lockfiles, and build outputs, and missing any one of them produces broken or inconsistent releases. This Skill guides the full release workflow so version bumps and publishes stay consistent.

Core Features & Use Cases

Release Build Workflow: Runs the make build process that cleans outputs, builds the root package, and collects provider package distributions.
Client Pin Bumps: Coordinates composio-client version updates across pyproject.toml, setup.py, and the root uv.lock file.
Publish Verification: Runs import checks and focused nox/Makefile validations after dependency changes.
Use Case: When bumping the composio-client dependency before a release, use this Skill to verify the version resolves on PyPI, update all pins together, regenerate the lockfile with uv, and confirm the package imports cleanly.

Quick Start

Use the python-release skill to bump the composio-client pin, regenerate uv.lock, and verify the build before publishing.

Frequently Asked Questions about python-release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I bump a Python dependency pin across pyproject.toml and setup.py?▼

Update the version in both python/pyproject.toml and python/setup.py together, then regenerate the lockfile from the repo root with uv lock --upgrade-package composio-client. Verify the new version resolves first using pip index versions composio-client.

How do I build a Python SDK package with make?▼

Run make build from the python/ directory after the environment is ready. It cleans build outputs, builds the root package, then builds provider packages and collects all distributions.

How do I verify a Python package after changing dependencies?▼

Run uv run --package composio python -c "import composio" to confirm the package imports cleanly. Then run the focused nox or Makefile checks relevant to the specific change.

When should I not use this Python release workflow?▼

Do not use it for ordinary Python feature implementation or bug fixes. It is scoped to release process work such as version bumps, packaging metadata changes, lockfile regeneration, and publish verification.