Repository navigation
PyHC Actions v1.2.0
What's changed
Behavior changes
- When run locally,
phep3-checknow uses the sameschedule.jsonas the GitHub Action: it downloads the latest release's copy, and falls back to a copy bundled with pyhc-actions when it can't. It prints which one it used. Regular (non-editable) installs no longer skip core package checks. (#32) - Both checks now exit 1 when given a path that doesn't exist, or a directory with no
pyproject.toml,setup.pyorsetup.cfg. Before, they could check a different project or pass. A directory argument now means that directory'spyproject.toml, and the default still works forsetup.pyandsetup.cfgprojects. (#32, #33) phep3-checknow warns when the schedule has no release data for a core package a project depends on, instead of silently skipping that package. Withfail-on-warning, this fails the check. (#34)
Fixes
pyhc-env-compat-checkno longer reports a false failure for packages built with Poetry's legacypoetry.masonry.apibackend, such as pyaurorax. (#31)- Schedule generation (releases, the monthly update and
--generate-schedule) now retries PyPI and refuses to save a schedule with missing core package data. (#34)
Usage
PHEP 3 Compliance Checker:
- uses: heliophysicsPy/pyhc-actions/phep3-compliance@v1.2.0PyHC Environment Compatibility Checker:
- uses: heliophysicsPy/pyhc-actions/pyhc-env-compat@v1.2.0Included Files
schedule.json- Current release schedule for Python and core Scientific Python packages