update-maturin

Upgrades maturin and regenerates the tapo-py GitHub Actions workflow while preserving local customizations.

797|80|Updated Jun 6, 2022
One-click install
npx skills add https://github.com/mihai-dinculescu/tapo --skill update-maturin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-maturin
Source: https://github.com/mihai-dinculescu/tapo/tree/main/.claude/skills/update-maturin
Command: npx skills add https://github.com/mihai-dinculescu/tapo --skill update-maturin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Regenerating a maturin CI workflow with maturin generate-ci github normally wipes out project-specific customizations, forcing maintainers to manually re-apply workflow names, triggers, manifest paths, and job labels after every upgrade.

Core Features & Use Cases

  • Dependency Upgrade: Bumps the maturin build tool to the latest release via uv lock --upgrade-package maturin and confirms the new version.
  • Workflow Regeneration: Runs maturin generate-ci github to produce a fresh baseline for .github/workflows/tapo-py.yml.
  • Customization Preservation: Re-applies project-specific settings such as the Tapo Python workflow name, branch/tag/path triggers, --manifest-path ./tapo-py/Cargo.toml args, manylinux: 2_28, job display names, the Test sdist step, and never-downgrade GitHub Actions versions.
  • Use Case: When a new maturin release ships, run this Skill to update the Python CI pipeline in minutes without losing any local workflow tweaks.

Quick Start

Update maturin to the latest version and regenerate the tapo-py GitHub Actions workflow while keeping all our customizations.

Frequently Asked Questions about update-maturin

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

FAQPage Schema
How do I update maturin to the latest version in a uv project?

Run `uv lock --upgrade-package maturin` followed by `uv sync` from the project directory, then verify with `uv run maturin --version`. If the version did not change, maturin is already at the latest release.

How do I regenerate a maturin GitHub Actions workflow without losing customizations?

Run `maturin generate-ci github` to capture a baseline, then edit the committed workflow to match the baseline while re-applying each documented customization. Diff the result against the baseline so only the intended customizations remain.

Does maturin generate-ci overwrite my existing workflow file?

The command prints the generated workflow to stdout rather than writing it directly, so the committed file is not overwritten automatically. You must merge the baseline into the existing file manually, preserving local changes.

Why should GitHub Actions versions not be downgraded when regenerating CI?

The maturin baseline may pin older action versions than the committed workflow. For each `uses: <action>@vN` line, keep the higher version between the current file and the baseline to avoid regressing to outdated actions.

What customizations does the tapo-py workflow keep after regeneration?

It keeps the Tapo Python workflow name, main-branch and v* tag triggers, pull_request path filters, the --manifest-path ./tapo-py/Cargo.toml flag, manylinux 2_28, Python-prefixed job display names, and a Test sdist step.