docs(changelog): add 0.2.1 entry for evaluate_batch hook#21
Merged
Conversation
Contributor
Author
|
Automated PR review (fresh adversarial reviewer) — APPROVE Verified against
No defects found. Ready to merge (G1); tagging/release remain separate human gates (G2). |
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.
What
Adds a
[0.2.1]section toCHANGELOG.md(dated 2026-06-29) documenting the optionalevaluate_batchhook onga()/nsga2()(whole-population batched fitness/objectiveevaluation, shipped in commit 5a69300), and fixes the changelog link references:
[Unreleased]now compares fromv0.2.1, and a new[0.2.1]release-tag link is added.Scope
CHANGELOG.mdis changed. No source, tests, workflows, or version bumps —pyproject.tomlis already at0.2.1and__version__is dynamic.Release note (human action required after merge)
This PR does not tag or release anything. After it merges, a maintainer should tag
v0.2.1and cut a non-prerelease GitHub Release, which triggersrelease.ymltopublish
ctrl-freak 0.2.1to PyPI via OIDC Trusted Publishing.