release: 2.1.6 - #108
Merged
Merged
release: 2.1.6#108
Conversation
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.
Version bump only: pyproject, README install snippets, uv.lock, CHANGELOG heading, regenerated RELEASE_CONTRACT.md.
2.1.6 ships the five fixes merged since 2.1.5, all found by rigorous testing of 2.1.5 on the live machine:
status/doctor/stop/kill-orphanswalk the adoption order instead of dict insertion order;restartreports the port it spawned on.get_instance_stateraises on a blocked storage read instead of reporting empty storage as the truth; messages never carry page values.SingletonLockno longer walks a named profile to<name>-2.Merge LAST, then tag
v2.1.6on the merge sha.