-
Confirm the working tree is clean and you're on the release
branch the user expects:
git status
git log --oneline -10
-
Bump the version in both files.
pyproject.toml: version = "<new>" under [project].porosity_fe/__init__.py: the __version__ = "<new>" fallback
(the comment there explicitly says "keep in sync with
pyproject.toml on each release").
-
Update CHANGELOG.md. Add a dated section for the new version
following the existing style. Pull the entries from git log <previous-tag>..HEAD --oneline and group them into Added / Changed /
Fixed / Removed. Don't invent entries — every line should map to a
landed commit.
-
Run the local gate (must mirror .github/workflows/tests.yml):
ruff check .
pip install "numpy<2"
mypy porosity_fe porosity_fe_analysis.py
pip install "numpy>=1.20"
python -m pytest tests/ -v
python -c "import app; print('app imports OK')"
-
Rebuild the standalone CLI to verify the PyInstaller spec still
works and the validation datasets bundle cleanly:
pip install pyinstaller
python -m PyInstaller ValidatePorosity.spec --noconfirm --clean
./dist/validate_porosity/validate_porosity --help
./dist/validate_porosity/validate_porosity --output-dir /tmp/rel-check
Confirm validation_master_report.png + validation_detail_report.md
are produced and the aggregate MAEs match what the README claims (if
they drift past a tenth of a percent, update the README before
tagging).
-
Stop here and hand back to the user for the actual tag + push.
Do not run git tag or git push --tags from the skill. Print
the suggested commands instead:
git add pyproject.toml porosity_fe/__init__.py CHANGELOG.md
git commit -m "release: v<new>"
git tag -a v<new> -m "v<new>"
git push origin <branch> --follow-tags
Confirm the version, changelog headline, and gate results in your
reply so the user can sanity-check before pushing.
