deployment-git

Coordinate Git workflows and CI/CD pipelines to publish multi-package SDKs to PyPI.

Updated Oct 10, 2025
One-click install
npx skills add https://github.com/FFOO6866/lead2cash --skill deployment-git-ffoo6866
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deployment-git
Source: https://github.com/FFOO6866/lead2cash/tree/main/.claude/skills/10-deployment-git
Command: npx skills add https://github.com/FFOO6866/lead2cash --skill deployment-git-ffoo6866

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents broken or inconsistent SDK releases by coordinating Git workflow, multi-package version bumps, CI/CD publishing, and documentation deployment so that what gets tagged, built, validated, and published stays aligned across every package.

Core Features & Use Cases

  • SDK release onboarding: Guides creating the project’s release infrastructure so publishing, versioning, and validation happen correctly from the start.
  • CI/CD release workflows: Covers GitHub Actions patterns for wheel building across platforms, TestPyPI validation, PyPI publishing, and GitHub release creation.
  • Multi-package atomic release coordination: Ensures dependency order, reverse publish wave, and version consistency across all related Kailash sub-packages to avoid ecosystem version-skew.
  • Git workflow best practices: Provides branching/PR/tag conventions that reduce release-time surprises and protect mainline stability.
  • Docker/Kubernetes deployment patterns (reference): Includes quick patterns for deploying containerized Kailash apps where needed alongside SDK release work.

Quick Start

Use the deployment-git skill to set up and execute a safe release workflow for your SDK by running the Git-tag-triggered pipeline steps and validating each package on TestPyPI before publishing to production PyPI.

Frequently Asked Questions about deployment-git

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

FAQPage Schema
How do I publish a multi-package SDK to PyPI without causing version skew across dependencies?

To publish a multi-package SDK safely, coordinate a reverse dependency-wave publish order with strict version consistency verification across all packages before triggering PyPI uploads. This prevents ecosystem version-skew by ensuring every related sub-package is validated and aligned atomically.

What's the best way to automate wheel building and PyPI publishing through GitHub Actions?

Automate wheel building and PyPI publishing by configuring GitHub Actions patterns that build wheels across platforms, validate artifacts on TestPyPI, and only trigger production PyPI publishing after CI passes and Git tags are created.

How does TestPyPI validation work before a production release?

TestPyPI validation works by building wheels, uploading them to TestPyPI first, and verifying the package installs and imports correctly from the test registry before publishing to production PyPI, ensuring broken releases never reach end users.

Can I prevent committing code or publishing packages when CI is failing?

Yes, you can prevent committing and publishing with failing CI by enforcing guardrails in your Git workflow and GitHub Actions pipeline that block merge, tag creation, and publish steps until all continuous integration checks report success.

Do I need specific Git branching and tagging conventions for safe SDK releases?

Git branching and tagging conventions are required for safe SDK releases to reduce release-time surprises and protect mainline stability. Establish PR conventions, release branches, and consistent tag triggers before configuring any automated publish pipeline.

Why does multi-package atomic release coordination matter for SDK onboarding?

Multi-package atomic release coordination matters because it enforces dependency ordering, reverse publish waves, and version consistency across SDK sub-packages, preventing partial releases that break downstream integrations when users install related packages simultaneously.