Repository navigation
docs: disclose unchanged benchmark measurements through v1.4.0 - #360
Merged
Merged
Conversation
Extend the README's no-remeasurement sentence from 542a559, whose release list ended with "v1.2.0 and v1.3.0", to include v1.4.0 using the approved disclosure wording. No commits changed benchmarks/results between the v1.3.0 and v1.4.0 tags; both retain the same results tree. Keep the 2026-09-29 refresh date, measured engine/codegen pins, hardware, tiers, timings and links unchanged. The README, docs/pages and benchmarks search found no other copy of this benchmark release list. Leave unrelated release/ABI lists and the existing tutorial 1.4.0 disclosure unchanged. Co-Authored-By: Codex <noreply@openai.com>
luisleo526
marked this pull request as ready for review
October 8, 2026 09:09
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.
The benchmark disclosure stopped at v1.3.0. Add v1.4.0 to state explicitly that neither the tiers nor the timings were re-measured for that release.
This is one clause change in README.md. Searches of README, documentation pages and benchmarks found no other copy. The recorded refresh date, measured revisions, hardware, results and unrelated version lists are unchanged; both release tags retain the same benchmark-results tree.
Validation on head
3abed4618901eb04441b0f7a0563c8c3604b2909: