0.18.2 - #80
Merged
Merged
0.18.2#80
Conversation
Four behaviour changes have been sitting on main since 0.18.1 shipped on 2 August, and one of them prevents a silent wrong answer: - `includes` refuses a field the schema says is a scalar (a365214). Before this, `filter the orders where title includes "roof"` validated clean, emptied a two-record list, and reported success. - A fired prohibition reaches the process exit status, and `includes` after `where` survives the reorderer (f9f0909). - A quoted value that shadows a declared predicate keeps its quotes through canonical rendering (8963d13). `require total is "large"` was rendering as `require total is large`, which re-parses as a predicate application — the same text, a different program. Plus the conformance corpus itself (e6195c4) and the node-kind gate over it (6526b0a), which is what found the last of those. The fixture is renamed rather than duplicated: it is named for the version it describes, and the fixture-exists test requires one for the current version. Contents are unchanged apart from `language_version` — the bump itself changes no behaviour. 1902 tests pass. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01E6qcDj1e1dEYvc8jLnpGZy
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
1 participant
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.
Cuts the release for four behaviour changes that have been sitting on
mainsince 0.18.1 shipped on 2 August.a365214includesrefuses a field the schema says is a scalar. Before this,filter the orders where title includes "roof"validated clean, emptied a two-record list, and reported success.f9f0909includesafterwheresurvives the reorderer8963d13require total is "large"was rendering asrequire total is large, which re-parses as a predicate applicationPlus the conformance corpus (
e6195c4) and the node-kind gate over it (6526b0a), which is what found the last of those.The fixture rename
tests/fixtures/conformance-0.18.1.json→conformance-0.18.2.json. It is named for the version it describes, andtest_the_generated_fixture_matches_the_version_it_was_generated_fromrequires one matchingpyproject.toml. Renamed rather than duplicated; contents unchanged apart fromlanguage_version, since the bump itself changes no behaviour.Verification
1902 tests pass. The corpus gate is green at the new version (57 cases, node coverage 39 of 43).
Follow-up
@liminate/ts-validatorcarries its own copy of the fixture, still namedconformance-0.18.1.json. A PR renaming it follows — no content change there either, but leaving the name stale is exactly the class of drift the corpus exists to stop.🤖 Generated with Claude Code
https://claude.ai/code/session_01E6qcDj1e1dEYvc8jLnpGZy