Index of every page on this site: llms.txt
All skills
composiohq avatar

/python-release

@85dab73
by Composiocomposiohq/composio31k stars
4,962
Run it yourself

Handle Python SDK release, build, bump, packaging metadata, PyPI client pin, uv.lock, nox/build workflow, and publish verification changes. Use for Python release process work or dependency pin bumps; do not use for ordinary Python feature implementation.

Use this Skill: https://skilld.dev/gh/composiohq/composio/python-release

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesrelease-workflow.md

≈538 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Python Release Workflow

Build

Run from python/ after the environment is ready:

make build

make build cleans build outputs, builds the root package, then builds provider packages and collects distributions.

Stable and beta Python releases use the unified sdk.release.yml member request and one approved release PR; a beta publishes X.Y.ZbN for core and every provider. Author changesets for the private @composio/python-sdk marker; the release bot synchronizes core and all supported provider metadata. Read ts/docs/internal/release.md for request, approval, merge, recovery and owner setup steps.

Recovery: re-run a failed tag run with gh run rerun <tag-run-id> --failed. When the approved candidate expired, add a changeset and request a new release. Agents stop at "release PR ready for approval" and never merge it.

Candidate builds install only the release dependency group from uv.lock with uv sync --locked --only-group release and use BUILD_ARGS=--no-isolation. Bump build or setuptools in that group, then run uv lock. Stable publication uses the tag-only pypi-release OIDC environment. The legacy py.release.yml keeps build-only dispatch and core-prerelease publication through pypi.

Dependency Bounds

Third-party runtime dependencies carry an upper bound at the next major line after the newest release available when the cap was set (<1 for 0.x packages). certifi stays uncapped so CA bundle updates always install. pysher is pinned exactly because it is unmaintained. Keep pyproject.toml and setup.py identical for each package.

Client Pin Bumps

Before bumping composio-client, verify the version resolves:

pip index versions composio-client

Update all Python pins together:

  • python/pyproject.toml
  • python/setup.py
  • root uv.lock

Regenerate the lockfile from the repo root:

uv lock --upgrade-package composio-client

Verification

Run import and package checks after dependency changes:

uv run --package composio python -c "import composio"

Then run the focused nox/Makefile checks relevant to the change.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2d3 checks · Risk SAFE
  • Gen Agent Trust Hub2d

    The skill facilitates Python SDK release workflows, including building, dependency management, and import verification using standard tools like uv, make, and the GitHub CLI. It interacts with the vendor's own packages and official registries. Security findings are limited to the inherent risks of automated command execution based on documentation.

  • Socket14d

    No alerts

  • Snyk2d

    Risk: LOW · No issues

Signed by skilld at 85dab73. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 5 months ago

README badge

README badge for composiohq/composio/python-release