Repository navigation
Fix the title and due date of an issue that merges two versions - #126
Merged
Merged
Conversation
An issue that covers several versions of a dependency took its title's "from" and its due date's release list from whichever version was merged in first. When the minimum version came from another version's spec, the title could ask for a release below the "from" version, and the due date counted from a release the title did not ask for. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
irskep
changed the title
mblair
approved these changes
Oct 16, 2026
srubin
approved these changes
Oct 16, 2026
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.
An issue that covers several versions of a dependency took its title's "from" version, and the release list behind its due date, from whichever version was merged in first. When another version's spec set the minimum version, the two halves of the issue came from different upgrades.
Worked example. A team is on
test-pkg2.0.0 and 1.2.0. Latest is 3.0.0. Releases: 1.2.5 on Feb 1, 2.0.3 on May 1, 3.0.0 on Jun 1.Before, with 2.0.0 merged in first:
The title asks for a release below the version it names. The due date is 28 days after 3.0.0, the first major above 2.0.0, because 1.2.5 is not in 2.0.0's release list.
After:
The issue remembers which version's spec set the minimum, and the title and due date come from that version. Group issues do the same for each dependency. An issue with one version is unchanged.
🤖 Generated with Claude Code