prefire

Placeholder release reserving the prefire name on PyPI.

Status: not implemented yet. Version 0.0.1 is a placeholder so the name is taken; real functionality lands in a later release.

Install

pip install prefire

Usage

prefire --version

Development

python -m venv .venv
.venv/bin/pip install -e ".[dev]"   # Windows: .venv\Scripts\pip
pytest
ruff check .

Release

Publishing runs on GitHub Actions via PyPI Trusted Publishing, so no API token is stored anywhere.

One-time setup

1. On PyPI, add a pending publisher at https://pypi.org/manage/account/publishing/:

   Field	Value
   PyPI project name	prefire
   Owner	cxnt
   Repository name	prefire
   Workflow name	python-publish.yml
   Environment name	pypi

2. In this repository, create the pypi environment under Settings → Environments (optionally add a required reviewer, so a release cannot upload without approval).

3. Optional: repeat both steps on https://test.pypi.org with environment name testpypi to enable dry-run uploads.

Cutting a release

1. Bump __version__ in src/prefire/__init__.py.
2. Commit and push to main.
3. Create a GitHub Release with tag vX.Y.Z (matching the bumped version).

The workflow builds an sdist and wheel, runs twine check --strict, verifies the tag matches the packaged version, and uploads to PyPI. To dry-run against TestPyPI instead, run the Publish workflow manually with target testpypi.