Releases: dougfirlabs/scholialang
Release list
scholialang 0.7.2
Patch release hardening constraint validation while preserving the stable Scholia v0.6.2 language grammar.
- Correctly parses article-bearing constraints such as “Never a bare null.”
- Uses full token boundaries and case-insensitive forbidden-phrase matching.
- Adds shared positive/negative conformance fixtures and release-version guards.
- Preserves forward-only constraint scope.
scholialang 0.7.1
scholialang 0.7.1 — first synchronized suite release
Additive fingerprint= attribute (contract-approved). No behavior change for
existing traces. 0.7.0 skipped intentionally so scholialang and scholialang-mcp
share one version line.
scholialang v0.6.2
What's Changed
Full Changelog: v0.6.1...v0.6.2
v0.6.1
The <Concluding> status release. A <Concluding> may now carry an
optional status attribute recording the terminal disposition of the
Goal it closes, aligning the reference parser/validator with the ratified
v0.6.1 spec contract.
<Concluding status=...>—statusis an optional enum
(met|unmet|partially_met) on theConcludingdataclass and in
KIND_SPECIFIC_FIELDS['Concluding']. The parser accepts it, the
serializer round-trips it, andcompute_canonical_idfolds it into the
content hash only when present. A status-less<Concluding>parses and
validates exactly as before (v0.5/v0.6.0 back-compat).- Validator — when
statusis present it must be one of
met|unmet|partially_met; an out-of-enum value is a hard validation
error (under thev031_optional_fieldsrule). Thegoal_declaredrule
now readsConcluding.status: a required Goal is closed by a status-less
Concluding (back-compat) or one carrying an in-enum status. - Versions — the package version (
pyproject+__version__) and
SCHOLIA_VALIDATOR_VERSIONboth move to0.6.1. The registry format
version stays0.6(it tracks the on-disk format, not the patch). - Publish hygiene — internal references were scrubbed from
src/,
tests/, and fixtures, and a CI leak guard
(tests/unit/scholia/test_public_hygiene.py) now hard-fails on the
forbidden token set acrosssrc/,tests/, andscripts/. - Registry DAG naming — the registry's in-memory return type is now
VerificationDag(a content-addressed DAG of verification relationships,
not a linear chain), surfaced viawalk_dag/to_verification_dag/
dag_to_dict/dag_from_dictand backed by the
scholialang.verification_dagshim. The default on-disk registry path
becomes~/.scholia/registry.verification_dag.json. This settles the
interim v0.6.0 DAG-shape naming before the v0.6.1 publish, so the
registry's public surface debuts under the accurateverification_dag
name rather than the inaccurate "chain" framing.
scholialang v0.6.0
Initial public PyPI release of the Scholialang reference implementation.\n\nHighlights:\n- v0.6 content-addressable canonical_id substrate\n- Canonical-id-aware parser and validator\n- DAG registry and lazy prelude support\n- MIT OR Apache-2.0 licensing