0.1.8: the LadybugDB retraction fix belongs in this release's notes - #124
Merged
Merged
Conversation
#123 merged after the release commit, so `main` carried the fix while the 0.1.8 section said nothing about it. 0.1.8 is not published and not tagged, so the release's contents are not frozen: folding the entry in is correct and leaves no version gap, where shipping it as 0.1.9 would have meant publishing twice for one batch of work. The entry carries the same weight as the other four — what broke, how it surfaced, which options were rejected and why, and what the migration can and cannot recover. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Shashankss1205
added a commit
that referenced
this pull request
Sep 26, 2026
#127 and #126 merged after the release commit and neither is in the notes. 0.1.8 is still unpublished and untagged, so folding them in is correct for the same reason #124 did it for #123. The reclaim gets a full entry: it changes shipped behaviour and adds a public method, and the entry is explicit that it closes a documented *limitation* rather than a defect -- which comes to the same thing for whoever hit it. What it refuses, and why nothing calls it automatically, are the load-bearing parts and are stated. The styling gate goes in the tooling paragraph, where it belongs: it changes no shipped behaviour, it changes what a regression in shipped behaviour would be caught by. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Shashankss1205
added a commit
that referenced
this pull request
Sep 26, 2026
#115 and #129 merged after the release commit. 0.1.8 is still unpublished and untagged, so folding them into its notes is right for the same reason #124 and #128 did it. The research registry gets a full entry: it is a shipped module and it closes the gap that the planner's headline capability -- decomposition -- was the one with no runnable example, while the only registry in the box demonstrated refusal. Credited to @only-ouc, whose pull request it is. The drift job's wheel walk goes in the tooling paragraph beside the styling gate: it changes nothing shipped, it changes what a break in shipped behaviour would be caught by. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
#123 merged after the release commit, so
maincarries the #110 fix while the## 0.1.8section of the changelog says nothing about it.0.1.8 is not published and not tagged — PyPI is still on 0.1.7 — so the release's contents are not frozen. Folding the entry in is the correct fix and leaves no version gap. Shipping it as 0.1.9 instead would mean publishing twice for one batch of work, and skipping a version on PyPI for no reason.
The entry carries the same weight as the other four in that section: what broke, how it surfaced, which alternatives were rejected and why, and what the migration can and cannot recover.
After this,
dist/needs rebuilding so the artifacts match — the wheel currently indist/predates #123.🤖 Generated with Claude Code