Repository navigation
Prepares the 9.4.4 release - #246
Merged
Merged
Conversation
`@version` moves to 9.4.4 and `CHANGELOG.md` gains a dated 9.4.4 section assembled from the one `changelog.d/` fragment, which this commit deletes. The functional change it releases: ordering two lists, or two maps, now compares two date members, or two datetime members, by instant, as a top-level pair already did. The section's lead names that one changed answer and says the conformance corpus hash moved, so a sibling implementation re-vendors at 9.4.4. A patch: the change touches private functions in the evaluator only; no opcode, error reason or public type is added, and the manifest's `isa_version` stays 6. The README install pin (`~> 9.4`) does not move. No tag is created here; the tag push publishes through the release workflow. Refs: px-neop
Codecov Report✅ All modified and coverable lines are covered by tests. 🚀 New features to boost your workflow:
|
johnnyt
added a commit
that referenced
this pull request
Oct 11, 2026
ADR-0019's Status line now reads accepted, naming predicator 9.4.4, the version that carries its code: the change landed in #245, the release prep #246 merged at ecff778, and the tag v9.4.4 on that commit published through run 38095733683 on its first attempt. The index row in docs/adr/README.md reads accepted. A dated foot Note records the evidence and the SHA of origin/main at which every claim the record makes was re-verified today; no claim had moved, so no sentence is superseded. The flip was decided by the conductor under a standing consent, 2026-10-10. Only docs/adr/ changes: the Status line and the index row are the only removed lines. No Elixir touched, no gate run. Refs: px-9seb
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prepares the predicator 9.4.4 release:
@versionmoves to 9.4.4, the onechangelog.d/fragment is assembled into a dated 9.4.4 section ofCHANGELOG.mdwith a lead paragraph, and the fragment is deleted. The README install pin (~> 9.4) does not move: a patch leaves it.No tag is created here. Once this merges, the tag
v9.4.4at the merge commit publishes through the release workflow.What 9.4.4 releases
Since
v9.4.3two commits landed on main: the evaluator change that orders date members of lists by instant, and the acceptance of the release-workflow record (docs only, no fragment). The one changed answer: ordering two lists, or two maps, now compares two date members, or two datetime members, by instant, as a top-level pair already did. A pair at the same instant steps to the next member; equality, membership, mixed date and datetime members and every top-level answer keep their 9.4.3 answers.The closed-set question
git diff v9.4.3..origin/main --stat -- lib conformancelistslib/predicator/evaluator.exand four files underconformance/: the dates case file, the tier 1 corpus file, the manifest and the registry example.lib/predicator/evaluator.ex: a new privatecompare_values/3clause for two lists or two plain maps under an ordering operator, and the new private helpersorder_members/2,order_map_values/2andorder_terms/2. All aredefp; no public function, opcode, error reason, value type or other set a host pattern-matches gains a member.conformance/manifest.json:isa_versionstays 6 and every tier's opcode list is unchanged; tier 1'scase_countand thecorpus_hashmove (below).No promoted change grows a closed set or a public union, so the release is a patch.
Corpus
No corpus file changes in this PR. The corpus moved on main with the evaluator change: five
dates/member cases joined tier 1 (dates/date-list-level-member-steps-to-next,dates/datetime-list-level-member-steps-to-next,dates/gt-date-list-members-by-instant,dates/lt-date-list-members-by-instant,dates/lt-datetime-list-members-by-instant), and the corpus hash advanced fromsha256:bb60ec82...tosha256:ddc5cf82.... A sibling implementation re-vendors the corpus at 9.4.4; the section's lead says so.The CHANGELOG section
The bullet is the fragment's text, rewrapped.
Gate
mix qualityon the staged tree of this commit, green. The quality report, whole:The lines before it in the run are dependency compilation in a fresh worktree.