pyincore‐data: Release Notes for Maintainers

Repo-specific companion to Release Process, which has the branch model, squash rules, CHANGELOG format, semver guide and tagging convention. Read that first; this page only records what is different here.

Branches	develop (default), main
Release branch form	⚠️ no release-* branches exist
Tag form	v1.0.0, RC v1.1.0rc1
Latest release	v1.0.0
Version source of truth	pyincore_data/globals.py → PACKAGE_VERSION
Published as	conda (IN-CORE channel) + PyPI
CI publish trigger	GitHub release published

Bumping the version

./version.sh 1.1.0

Release candidates

Same tag-driven mechanism: v1.1.0rc1 → Test PyPI + conda rc label.

This repo's environment.yaml already lists in-core/label/rc as a channel, so it picks up unreleased pyincore RCs by design. Be deliberate about that at release time — a final release should not depend on an RC.

Before releasing

python -m pytest --cache-clear -s tests/pyincore_data/test_pyincore_data.py

CI runs only that one file. tests/pyincore_data/test.py and test_nsi.py exist and are never run — run them by hand before a release.

Watch out

• The env file is environment.yaml, not environment.yml like its siblings.
• There is no requirements.sh here. setup.py reads requirements.txt directly, so requirements.txt and environment.yaml must be kept in sync by hand.