Correct OptimizationBase to the next sequential release - #1290
Merged
ChrisRackauckas merged 1 commit intoJul 29, 2026
Merged
Conversation
Master carries 5.2.4, which jumps over the unregistered 5.2.3 relative to the latest registered release 5.2.2, so AutoMerge rejects the registration under the sequential version number guideline. 5.2.3 was never released, so lowering to it loses no history. Every in-repo compat bound on OptimizationBase is "5" or "5.1", both of which 5.2.3 still satisfies, so no sibling becomes uninstallable. Co-Authored-By: Chris Rackauckas <accounts@chrisrackauckas.com> Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VNsHcCmMeNCWuN8BNR8RJr
ChrisRackauckas
marked this pull request as ready for review
July 29, 2026 19:46
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
2 participants
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.
Please ignore until reviewed by @ChrisRackauckas.
OptimizationBasecarries5.2.4on master, which jumps over the unregistered5.2.3relative to the latest registered release5.2.2. AutoMerge rejects this under the sequential version number guideline, soOptimizationBasecannot currently register — and because 24 sibling subpackages depend on it, nothing else in this repo can register either.One line, one file.
5.2.3was never released, so no published history is lost.No compat bound is invalidated
Lowering a version can make a sibling
[compat]bound unsatisfiable. Every in-repo bound onOptimizationBaseis either"5"or"5.1", both of which5.2.3still satisfies, so no dependent becomes uninstallable and no bound needs to move here.Context
Found while sweeping SciML for packages whose released state disagrees with master. The other 24 packages in this repo are at exactly their registered version with unreleased
srcchanges, so they need ordinary version bumps rather than corrections — that is a separate PR, and it should land after this one soOptimizationBaseregisters first.