python-gen-tarball

Rebuild and stage the proto-python-gen tarball when sources change.

49|15|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/block/proto-fleet --skill python-gen-tarball
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: python-gen-tarball
Source: https://github.com/block/proto-fleet/tree/main/.claude/skills/python-gen-tarball
Command: npx skills add https://github.com/block/proto-fleet --skill python-gen-tarball

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures that the versioned Python proto generator tarball is rebuilt and published whenever sources under packages/proto-python-gen/ or edits to scripts/pip-config.sh occur, preventing downstream consumers from using stale code.

Core Features & Use Cases

  • Rebuild and package the proto-python-gen tarball whenever the relevant sources change.
  • Enforce version bumps and ensure the new tarball proto-python-gen-<version>.tar.gz is staged for commit.
  • Use case: maintainers update the Python generator and rely on Hermit to consume the updated tarball without breaking builds.

Quick Start

Run the packaging workflow to rebuild and commit the updated proto-python-gen tarball.

Frequently Asked Questions about python-gen-tarball

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

FAQPage Schema
How do I automate rebuilding a Python proto generator tarball when sources change?

Automating proto generator tarball rebuilds involves enforcing version bumps in the justfile and running just package to create proto-python-gen-<version>.tar.gz, staging the updated tarball for commit to prevent downstream consumers from using stale code.

Why do downstream environments use stale Python proto generator code after source updates?

Downstream environments use stale Python proto generator code because the versioned tarball was not rebuilt and staged for commit. You must execute the packaging workflow to generate the updated proto-python-gen-<version>.tar.gz whenever sources under packages/proto-python-gen/ change.

What is the best way to enforce version bumps for Python proto packaging?

Enforcing version bumps for Python proto packaging requires updating the justfile located in packages/proto-python-gen/ before running just package, ensuring the generated tarball reflects the new version and is properly staged for commit.

How do I package a Python proto generator tarball using just?

Packaging a Python proto generator tarball using just requires executing the just package command after modifying sources, which creates the proto-python-gen-<version>.tar.gz file and stages it for commit while scanning for hard-coded references.

When do I need to rebuild the proto-python-gen tarball?

You need to rebuild the proto-python-gen tarball whenever modifications occur under packages/proto-python-gen/ or scripts/pip-config.sh, ensuring downstream Hermit environments consume the updated generator without breaking builds.

Does the proto-python-gen packaging workflow scan for hard-coded references?

Yes, the proto-python-gen packaging workflow scans for hard-coded references while staging the newly built proto-python-gen-<version>.tar.gz for commit, ensuring version consistency across the downstream environments consuming the updated generator.