Repository navigation
docs: add the 1.6.0 (Unreleased) entry to the changelog - #203
Merged
Merged
Conversation
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.
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
1 participant
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 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.
🤖 Generated with Claude Code