Prepare sunfish 2026.2 - #268
Closed
thomasahle wants to merge 1 commit into
Closed
Conversation
Owner
Author
|
Closing at the maintainer’s request: keep the release identity at sunfish 2026 and do not publish another tag. #265 remains merged and deployed. |
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.
What
Publish the R4 shallow-null improvement that landed immediately after the
v2026.1tag:2026.2;No engine code changes in this PR. The engine change is merged as #265 and is
already deployed to the classic Lichess bot.
Verification
uv lock --check: passed;git diff --check: passed.After merge,
tools/deploy.sh pypi v2026.2will verify master CI and push theimmutable tag, triggering the existing PyPI and GitHub release workflow.