Skip to content

docs: the 1.5.0 release (changelog, current pair, HPO note) - #374

Merged
luisleo526 merged 3 commits into
mainfrom
sm/engine-release-prep-1350b
Oct 12, 2026
Merged

luisleo526 merged 3 commits into
mainfrom
sm/engine-release-prep-1350b

Conversation

@luisleo526

Copy link
Copy Markdown
Collaborator

Documentation for the 1.5.0 release. Docs only: 8 files, no source, test or script change.

  • CHANGELOG.md: the 1.5.0 entry, dated 2026-10-12, including the new installed header <pineforge/native_calc_point.hpp>.
  • README.md, docker/README.md, docs/outputs.md: the current engine and codegen pair, status words for a released 1.5.0, and the HPO compatibility note: pineforge-hpo 0.13.2 pins pineforge-codegen <1.4; support for codegen 1.4 and 1.5 comes in pineforge-hpo 0.14.0.
  • docs/pages/{abi-stability,index,public-contract,run-failure-codes}.md: the current-release lines, and native_calc_point.hpp in the native C++ API list.

The 1.4.0 current-release sentence in README.md (introduced by 5a1ad3a) is replaced on purpose. It is kept in the Releases list and in the CHANGELOG 1.4.0 entry.

Checks: doc-lint, doc-anchors, doc-reverts, preflight (49 stages, 0 advisory) and the docs build (0 Doxygen warnings) passed in lab remote job a new lab remote job at this head (tree 776a3cb2, rebased by cherry-pick onto main 2394ba2; replaces #372).

🤖 Generated with Claude Code

luisleo526 and others added 3 commits October 12, 2026 18:14
Date the CHANGELOG's 1.5.0 entry 2026-10-13 and give it the release link
line naming the paired pineforge-codegen 1.5.0, keeping the recorded-outputs
and call-scoped-report content unchanged. Add the release's other
user-visible changes: the test inputs and strategy scripts moved to a
private repository, where a test that needs one skips with the pinned
message naming the missing file; the LEGAL.md "Data not distributed"
section; and the private-fixture overlay the maintainers run the
verification with.

README: the current-release block, the codegen command-block pointer, the
C ABI counts line and a new v1.5.0 Releases bullet now name 1.5.0; the
v1.4.0 descriptions, scoreboard and benchmark measurements stay untouched.

The current-release block's 1.4.0 sentence from 5a1ad3a ("The release notes
cover typed and unresolved provenance, coded failures, checked settings,
adapter fixes and chart-clock live input") is replaced on purpose by the
1.5.0 sentence that lists what 1.5.0 covers; that 1.4.0 summary stays in the
Releases list (the v1.4.0 bullet) and in CHANGELOG.md's 1.4.0 entry.

docs/pages/public-contract.md: the 1.5.0 paragraph follows the 1.4.0 one
and the same-version pairing line now says 1.5.0.

Scoreboard and benchmark numbers are untouched; no file outside these
three changes.
The CHANGELOG's 1.5.0 entry gains its HPO bullet: pineforge-hpo 0.13.2
pins pineforge-codegen <1.4, and HPO support for codegen 1.4 and 1.5
(enum options as Enum.member tags) comes in pineforge-hpo 0.14.0.

Five files that still called 1.5.0, or a 1.5.0 feature, unreleased or
targeted for it now read as released once the tag lands:
docs/pages/abi-stability.md (the RunFailureCode exception, the
symbol-inventory counts line, the recorded-outputs line),
docs/pages/index.md (its counts line, matching the README wording),
the run-failure page (the outputs and selected-window rows' status, the
two 1.5.0 outputs reasons, and the 24 catalog rows that said none was
released), docker/README.md (the recorded-outputs section) and
docs/outputs.md. Only the status words change; "not part of 1.4.0"
stays where it is true history, and no number, claim or other sentence
moves.

No file outside these six changes.

Co-Authored-By: Claude Code <[email protected]>
K1 (#369) added include/pineforge/native_calc_point.hpp, installed by the
include/pineforge rule in CMakeLists.txt with the other headers. Name it in the
1.5.0 CHANGELOG entry and in the native C++ API list of
docs/pages/public-contract.md (new in 1.5.0). Docs only.
@luisleo526
luisleo526 merged commit 4c78f39 into main Oct 12, 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