From 7d2ca16ad57e673697f32a1bd62b0b92049b6282 Mon Sep 17 00:00:00 2001 From: luisleo526 Date: Tue, 13 Oct 2026 17:35:54 +0800 Subject: [PATCH] docs: add the 1.6.0 (Unreleased) entry to the changelog The entry for the planned 1.6.0 release, in the form the 1.5.0 entry had at v1.5.0-rc.1: planned number, exact pair with engine v1.6.0 (1.6.0-rc.1 pairs with engine v1.6.0-rc.1), and the changes since 1.5.0 (#200, #201, #202). The analyzer and the code generator do not change behavior: the only edits under pineforge_codegen/ since v1.5.0 are comments and docstrings in five files (#202; the Python syntax tree of each file, docstrings removed, is identical to v1.5.0's), so the emitted C++ and the Python and JSON contract are unchanged. The entry says so and points to the release note policy for the regenerate-and-relink rule. The README, docs/ and VERSION are unchanged; the pairing row, the current-version lines and the date are set when the release is prepared. --- CHANGELOG.md | 34 ++++++++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 0d4e8e2..bce0604 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -20,6 +20,40 @@ supported as exact pairs; on the 0.x line they are independent. See the the release commit. A prerelease note describes changes since the preceding prerelease or stable tag; the final stable note consolidates the series. +## 1.6.0 — Unreleased + +The planned number of the next release; it stays **Unreleased** until its tag +exists, and the package version is unchanged. Codegen 1.6.0 is planned as the +exact engine/codegen pair with engine `v1.6.0`; the prerelease `1.6.0-rc.1` +pairs with engine `v1.6.0-rc.1`. This entry records what changed in this +repository since 1.5.0, and nothing else: the engine pairing, the date and the +final text are set when the release is prepared. + +### Compatibility and migration + +- The analyzer and the code generator do not change behavior: the only edits + under `pineforge_codegen/` since 1.5.0 are comments and docstrings in five + files (#202), so the C++ the transpiler emits for a script and the Python + and JSON contract are unchanged. No diagnostic code, severity or catalog + schema changes. +- The [release note policy](#release-note-policy) still applies: "A pair + change requires regenerated C++ and relinked strategy libraries, even + when the C ABI number is unchanged." Regenerate and relink against the + new engine's headers and static library. +- Engine behavior changes, including failure codes and the report contract, + are described in the paired engine's own release notes; this entry does + not summarize them. + +### Changes since 1.5.0 + +- Remove the 11 gate-corpus pines that copy probes leaving the engine corpus + ([#200](https://github.com/pineforge-4pass/pineforge-codegen-oss/pull/200)). +- Remove the subprocess time limits of CI tests and checks + ([#201](https://github.com/pineforge-4pass/pineforge-codegen-oss/pull/201)). +- Move the recorded US-listed, futures, forex and metal tapes of the tests to + the private fixtures, and reword the comments and docstrings that cited them + ([#202](https://github.com/pineforge-4pass/pineforge-codegen-oss/pull/202)). + ## 1.5.0 — 2026-10-12 A minor release of the exact engine/codegen pair, paired with engine `v1.5.0`