Repository navigation
Move to conformance-2026.19 - #83
Merged
Merged
Conversation
The level adds the five update cases, the update operation and the post-operation-epjson assertion, and removes the six typescript divergence entries for those cases, which #80 and #81 close. conformance.ts and the EPW sentinel table are regenerated from the new tag; only their recorded level changes. The publication gate's attested level moves with the pin, with the evidence taken at the tag in both languages.
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.
Summary
Raises the conformance pin from
conformance-2026.15toconformance-2026.19, the level at which both libraries carry the multi-fieldupdate(idfkit/idfkit#235) with no accepted divergence.conformance-2026.16conformance-2026.17update-*cases, theupdateoperation and thepost-operation-epjsonassertion (74 cases, 226 assertions).conformance-2026.18conformance-2026.19Changes
packages/core/package.json:idfkit.conformanceisconformance-2026.19.packages/core/src/conformance.tsandpackages/weather/src/epw-sentinels.ts: regenerated from the tag; only the recorded level changes.scripts/check-publication.mjs:REQUIRED_CONFORMANCEmoves with the pin, and its attestation records the evidence taken at the tag in both languages.CHANGELOG.md: an Unreleased note stating the level and what it adds.Evidence, taken at the tag
npm run check:releasepython runners/run.py --libraryon idfkit#236weather-check, both languagesgeometry-check, JavaScript and Python (--via get-sceneand--via translate-to-world)npm run typecheck,npm run format:check,npm run check:conformance-level,npm run check:sentinelsandnpm test(920 of 920) pass.Note on the Python pin
idfkit#236, which adds
IDFObject.update, pinsconformance-2026.18. The two levels differ only by the six typescript entries, so the Python result is the same at both, as recorded above. Raising idfkit to.19as well would put both libraries on the same level.