Skip to content

docs: disclose unchanged benchmark measurements through v1.4.0 - #360

Merged
luisleo526 merged 1 commit into
mainfrom
ar/rel140-benchmark-disclosure
Oct 8, 2026
Merged

luisleo526 merged 1 commit into
mainfrom
ar/rel140-benchmark-disclosure

Conversation

@luisleo526

Copy link
Copy Markdown
Collaborator

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:

  • Documentation reverts and whitespace checks passed.
  • Documentation preflight passed all 48 stages with 0 advisories.
  • Documentation build passed with 0 Doxygen warnings.
  • Independent narrow documentation review: MERGE.
  • The change is documentation only; required parity evidence is the recorded no-behavior-change diff, with no new benchmark or population measurement.

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
luisleo526 marked this pull request as ready for review October 8, 2026 09:09
@luisleo526
luisleo526 merged commit 31a40a1 into main Oct 8, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant