Skip to content

26.05.10

Choose a tag to compare

@timlichtenberg timlichtenberg released this 10 May 18:08
· 60 commits to main since this release
39308df

This release brings Zalmoxis to full conformance with the PROTEUS Ecosystem Testing Standard. There are no user-facing API or behavior changes; the surface is CI infrastructure, test discipline, and docs.

What's new

  • 95 percent coverage gate (#62): a hard fail_under = 95.0 in [tool.coverage.report], enforced in nightly via --cov-fail-under=95. 95 percent is the permanent ecosystem ceiling, not a ratchet. A PR pre-flight check rejects any PR that lowers fail_under relative to origin/main.
  • Four-marker pytest scheme: unit, smoke, integration, slow matching the PROTEUS main repo. --strict-markers and --strict-config enforced; tools/validate_test_structure.sh rejects any def test_* without exactly one tier marker (or skip).
  • CI workflow split: PR runs unit and not skip only, no coverage instrumentation, with concurrency cancel-in-progress on the branch ref. Nightly runs (unit or smoke or integration) and not slow with Codecov upload as the canonical coverage signal.
  • Test-quality fixes: three previously tautological assertions strengthened (Chabrier:H solvus detection, Gibbs-mixing inequality, inner-main non-converging post-break keys). Five # pragma: no cover walked back with positive coverage (Newton damping + Seager irregular grid + 3 paleos NaN-fallback paths).
  • Badges and docs: shields.io endpoint JSONs for total / unit / integration test counts, regenerated on push to main. New docs/Explanations/testing.md and docs/How-to/build_tests.md aligned with the ecosystem standard.
  • CODEOWNERS: review routed to @FormingWorlds/proteus-maintainer, matching the PROTEUS / ZEPHYRUS / CALLIOPE / JANUS / AGNI convention.

Validation

  • Last completed nightly: 95.44 percent on 4322 statements / 1420 branches.
  • Local unit tier pytest -m "unit and not skip" -n auto finishes in 21 s on the dev machine after validator-strict cleanup (down from 6:06 before).

Compatibility

No source-level changes to zalmoxis.* APIs. Existing pinning consumers (PROTEUS coupled runs, standalone grid driver) are unaffected.

Install

pip install --upgrade fwl-zalmoxis==26.5.10

Full changelog

26.05.07...26.05.10