v0.5.1
On this page
v0.5.1 carries Core specVersion 0.5.0 unchanged. It is the first patch release under the
release numbering rule of VERSIONING.md: a tag's major and minor numbers are
those of the specVersion it carries, and its patch number counts the later releases that carry it
unchanged. What it adds is beside Core: a proposed dialect format and the release tooling that builds
a patch release.
- Packs keep declaring exact
specVersion0.5.0. A pack declaring0.5.1is refused, because the Core schema'sspecVersionconstant is still0.5.0. - The tag name is not a selector.
0.5.1is this distribution's identity, as each bundle's generatedrelease-identity.jsonrecords it. No reader, pack or claim selects it. - Core
0.5.0's normative files are byte for byte those tagv0.5.0released: the Core text and schema, both corpus manifests, the cases and packs they name, and every schema whose$idis under0.5.0, as the recordreleases/v0.5.0.normative.jsonnames them. Both corpora keepsuiteVersion0.5.0. The builder refuses a patch tag, or a bundle, whose files differ from that record. The errata, the READMEs and the examples are not in the record. - Tag
v0.5.0still identifies Core0.5.0, and it is not changed or superseded. - Consumers pinned to
v0.5.0need do nothing.
Included work
- Dialect format
4.0.0, proposed (#316). An amendment of RFC 0018, a draft the maintainer has not yet decided, adds a third named format to the dialect companion (spec/dialect.md§2.2). It has: - a rule on the case, so that facts can be derived from a case the caller already holds, without a source;
- list parameters,
string-listandaddress-range-list, anddecimalparameters; - rule version
2.0.0, with ordered comparison of a value against a parameter, membership in a list parameter, a forward-looking freshness window and literal claim values; and - the built-in derived values
duration,distanceandspeed, in exact integer arithmetic, with the preparation form that records them.
Formats 2, 3, 2.0.0 and 3.0.0, their digests, preparations and vectors are unchanged, and
no answer to a document of one changes. The workflow schemas do not yet name the format.
- Its rows and its reader. 167 hand-written rows, one for each form and refusal, and two
end-to-end vectors are staged under conformance/dialect/format-4/. They are not a conformance
corpus, they are in no bundle, and no claim may cite them. The distances they expect come from
tools/dialect_builtins_reference.py, which computes them by another formula. The repository's
Python reader, tools/dialect_verify.py, reads the format. The TypeScript reader only refuses it,
version-unread, so no second independent reader exists and one reader's answers are the
vectors'. No preparer writes the format.
- Release tooling for a patch release (#314). The builder takes the specVersion a tag carries
from the tag's numbers, X.Y.0 for a tag vX.Y.Z, with v0.4.0 kept as the one recorded
exception. It refuses a patch tag whose normative artifacts differ from those its X.Y.0 release
recorded, and a patch tag of a specVersion that no release carries. In the record-shape check, a
patch tag is a baseline, not a candidate.
This release closes #316 and #314.
Compatibility
Nothing in Core moves, so each dimension VERSIONING.md names has the same answer between v0.5.0
and v0.5.1:
- Reader compatibility: unchanged. A
0.5.0reader reads what it read. - Writer compatibility: unchanged. Writers emit
specVersion0.5.0. - Semantic compatibility: unchanged. Conforming consumers assign the same portable meaning.
- Migration compatibility: no document transformation applies, because no Core document changes.
| Release | Core specVersion 0.5.0 |
Dialect format 4.0.0 |
|---|---|---|
Specification v0.5.0 |
released | not defined |
Specification v0.5.1 |
carried unchanged, byte for byte | proposed (spec/dialect.md §2.2); rows staged, in no bundle |
Reference runtime v0.44.0 and later |
read | no released version reads it |
| Reference Runner | as its own release notes state | no released version reads it |
Migration note
None. There is no specVersion to migrate to. A conformance claim stays against exact specVersion
0.5.0 and its corpora, and is neither widened nor renewed by this release. No claim names dialect
format 4.0.0, and a dialect document of an earlier format keeps its meaning.
The selected retained-column leaf
Stay on the v0.3.0 bundle for the retained-column/1 leaf, as for v0.5.0. That release is the
leaf's normative support distribution, and support version 0.3.0 does not change.
What is in the bundles
The .tar.gz and .zip bundles, with their checksums and build-provenance attestations, hold:
- the Core and companion prose under
spec/, without the Draftspec/workflow.md; schema/andconformance/, without the Policy companion's directories or the staged directories (conformance/dialect/,conformance/witness/,conformance/evaluation/staged/);examples/;catalog/, which a patch release's bundles carry;README.md,LICENSE,NOTICE,CHANGELOG.md,VERSIONING.md,TESTING.mdandSECURITY.md; and- this file, the record
releases/v0.5.0.normative.jsonand the generatedrelease-identity.json.
Of the files this bundle and the v0.5.0 bundle both hold, only these differ: README.md,
CHANGELOG.md, VERSIONING.md and spec/dialect.md, which gains §2.2.
They do not hold:
rfcs/, so the RFC 0018 amendment and its review are read at the tag or on the site;- the format
4.0.0rows and vectors, or any other dialect recording set; tools/, so the two dialect readers, the distance reference and the builder are read at the tag;requirements-dev.txt, the other files inreleases/, or the leaf inventories; or- the Policy companion's schemas and corpus, which keep their own
policy-vroute.
Versioning and maturity
Conformance manifest status stays draft. A patch release is not a candidate, so in
catalog/format-status.json this release is the baseline and the last release of the four families
whose $id is under 0.5.0: judgment-pack-core, conformance/manifest,
conformance/evaluation/manifest and workflow. The other families keep their records.
The builder holds this release, in the worktree and in each bundle, to the record
releases/v0.5.0.normative.json. It gives the SHA-256
of each of the 422 normative files of specVersion 0.5.0: the Core text and schema, both corpus
manifests, the cases and packs they name, and every schema whose $id is under 0.5.0. The record
was derived from the files of tag v0.5.0 (commit 171d4c21d4b13e03ee20e1adb6fc5cc6b182cfae), and
the builder pins the record's own SHA-256. Errata, READMEs and examples are not in the record.
Dialect format 4.0.0 is proposed: the maintainer has not decided the amendment, one reader reads
it, and it is not claimable.
What this release pins
- Format: exact
specVersion0.5.0, the Core schema'sspecVersionconstant and the selector both corpus manifests name. - Frozen corpora:
conformance/manifest.json(369 conformance cases and 5 advisory cases) andconformance/evaluation/manifest.json(103 rows, 29 pairs), bothsuiteVersion0.5.0at maturitydraft, byte for byte asv0.5.0released them. - Core schema:
https://judgmentpack.org/schema/0.5.0/judgment-pack-core.schema.json, SHA-256fb182fd0ab7fc303618ce9a63834616527a68b63b165e7ed3e76f48f29978da0, as inv0.5.0. - Document-manifest schema:
https://judgmentpack.org/schema/0.5.0/conformance/manifest.schema.json, SHA-256d835195ecf4c0f214d78d106256f9b61fa006d4888a1b7c115c65b837d0496ed. - Evaluation-manifest schema:
https://judgmentpack.org/schema/0.5.0/conformance/evaluation/manifest.schema.json, SHA-2567bc20cd13d074c56d151f90bd72ed8bed8d3bbd1481fcfe9218987652aafa1e8. - Workflow document schema:
https://judgmentpack.org/schema/0.5.0/workflow-1.schema.json, SHA-25674b13dc5b1cbf011ddefbb43490d4f615b20238033fd910feecfd10207e1907b. - Normative record:
releases/v0.5.0.normative.json, SHA-25686e175e8786eb6e08a215178ba7099edb074193c83c5ee2dc6a12012555b4aaa. - Distribution identity:
releaseVersion0.5.1, tagv0.5.1,specVersion0.5.0,distributionspecification-unchanged, with the source commit in each bundle'srelease-identity.json.
Checks run for this release
The release reuses main's repository-conformance evidence for this exact commit through the
release evidence gate (scripts/dev/release_evidence.py, configured by .github/ci-evidence.json)
instead of running the repository suite again. The milestone, tag, artifact-pin, normative-record and
bundle checks run again at the tag. The reused run's id and attempt are in the gate's decision
record, which the release run keeps as its release-evidence-<attempt> artifact
(web/DEPLOYMENT.md, "Release evidence").
The RFC 0018 amendment and its staged rows were reviewed in round 17 (rfcs/reviews/0018-round-17.md):
three MEDIUM and five LOW findings, all applied. That is same-vendor review, not a cross-vendor claim.
Each refusal the patch-release tooling adds has a test that fails when the refusal is removed.
Results against this release name its tag and commit. Conformance never proves truth, authorization, safety or operational fitness.