castorini-release

Name: castorini-release
Availability: InStock
Author: Castorini

Automate PyPI release workflows for Castorini projects with version bumps and publishing.

2|2|Updated Mar 17, 2026

Search Tags:#automation #workflow #release #pypi #preflight #version-bump #twine

Ready to run

npx skills add https://github.com/castorini/castorini-skills --skill castorini-release

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: castorini-release
Source: https://github.com/castorini/castorini-skills/tree/main/skills/castorini-release
Command: npx skills add https://github.com/castorini/castorini-skills --skill castorini-release

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

PyPI/Nuggetizer/ragnarok/rank_llm/umbrela release workflows are repetitive, error-prone, and siloed. This skill standardizes and automates the Castorini release process, ensuring version bumps, builds, checks, and publishing steps are performed consistently across repositories.

Core Features & Use Cases

Preflight and validation checks to ensure a clean state, correct version bumps, and build readiness before publishing.
End-to-end release sequencing across nuggetizer, ragnarok, rank_llm, and umbrela, including TestPyPI dry runs and production publishing.
Reference materials and scripts (references/) to guide and automate the publishing workflow and verify compliance with release practices.

Quick Start

Run the preflight script on your repository path to verify readiness, then follow the release sequence to build, test, and publish to PyPI.

Frequently Asked Questions about castorini-release

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

FAQPage Schema

How do I automate a PyPI release workflow for Python packages?▼

Automating a PyPI release workflow involves running preflight validation checks, applying bumpver version increments, building the distribution, and publishing via twine. This skill sequences those steps end-to-end to ensure consistent production publishing.

What is a TestPyPI dry run and when do I need it before a production release?▼

A TestPyPI dry run is a pre-publishing validation step that uploads your built package to a test repository instead of production PyPI. You need it to verify build integrity, metadata, and installation behavior before the final production release.

How do I manage version bumps consistently across multiple repositories?▼

Managing version bumps across multiple repositories requires standardizing on a tool like bumpver and applying it within an automated release sequence. This ensures version increments and tagging guidelines are enforced consistently across projects like nuggetizer, ragnarok, rank_llm, and umbrela.

Can I use preflight scripts to check build readiness before publishing to PyPI?▼

Yes, preflight scripts verify repository cleanliness, correct version bumps, and build readiness before publishing to PyPI. Running them on your repository path confirms that all validation checks pass and the package is ready for the release sequence.

What's the best way to standardize release processes for Castorini projects?▼

Standardizing release processes for Castorini projects involves applying an automated workflow that covers preflight checks, version management, builds, TestPyPI dry runs, and final production publishing across nuggetizer, ragnarok, rank_llm, and umbrela repositories.

Why does my PyPI release workflow fail due to siloed or inconsistent version tagging?▼

PyPI release workflows fail due to siloed or inconsistent version tagging when version bumps and checks are performed manually across repositories. Standardizing the release process with automated preflight validation and bumpver-based version management prevents these errors.