release

Coordinates multi-subprocess releases to PyPI and Docker Hub via GitHub Actions.

110|14|Updated Apr 1, 2025
One-click install
npx skills add https://github.com/memgraph/ai-toolkit --skill release-memgraph
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/memgraph/ai-toolkit/tree/main/skills/release
Command: npx skills add https://github.com/memgraph/ai-toolkit --skill release-memgraph

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Release management across Memgraph AI Toolkit subprojects can be error-prone and time-consuming; this skill provides a centralized, repeatable process to publish new versions to PyPI and Docker Hub via GitHub Actions workflows.

Core Features & Use Cases

  • Automates triggering and tracking multi-subproject releases (toolbox, integrations, and agents).
  • Documents required secrets, workflow files, and version bump steps for reproducible releases.
  • Use Case: A maintainer bumps the version in pyproject.toml and dispatches release workflows to publish updated packages.

Quick Start

Bump the version in the subproject's pyproject.toml and trigger the corresponding GitHub Actions release workflow.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate Python package releases to PyPI using GitHub Actions?

Automate Python package releases to PyPI by dispatching GitHub Actions workflows after bumping the version in pyproject.toml, using configured PYPI_TOKEN secrets to publish updated packages automatically.

What is the process for syncing version bumps across multiple subprojects before a release?

Syncing version bumps across subprojects requires updating the version field in each subproject's pyproject.toml individually before triggering their corresponding GitHub Actions workflows to ensure coordinated releases.

Do I need specific secrets configured to publish packages to PyPI and Docker Hub?

Yes, publishing packages requires configuring GitHub Actions secrets such as PYPI_TOKEN and DOCKERHUB_TOKEN to authenticate and push releases to PyPI and Docker Hub repositories securely.

Can I use this release workflow for both Python packages and Docker images?

Yes, the release workflow supports publishing to both PyPI and Docker Hub, coordinating multi-subproject releases for Python packages via pyproject.toml and container images via GitHub Actions.

Why does my automated release workflow fail after modifying pyproject.toml?

Automated release workflows fail if the pyproject.toml version field is incorrectly formatted or if required GitHub Actions secrets like PYPI_TOKEN are missing or invalid for authentication.

What's the best way to manage coordinated releases for a multi-package Python monorepo?

The best way to manage coordinated multi-package releases is centralizing the process via GitHub Actions, documenting required secrets, and standardizing version bump steps across subprojects for reproducible deployments.