Raise Mooncake compat floor to 0.5.36 (fix Downgrade resolution)#1241
Closed
ChrisRackauckas-Claude wants to merge 1 commit into
Closed
Raise Mooncake compat floor to 0.5.36 (fix Downgrade resolution)#1241ChrisRackauckas-Claude wants to merge 1 commit into
ChrisRackauckas-Claude wants to merge 1 commit into
Conversation
Replace the `Mooncake = "0.4.138, 0.5"` union in the root Optimization and OptimizationBase [compat] sections with a single floor at the latest Mooncake `0.5.36`. The old union let the Downgrade CI min-resolution pin an ancient Mooncake (0.5.15), the promotion of which drove the Resolver.jl Unsatisfiable wall. Pinning the floor to the latest keeps the downgrade resolvable. Patch-level version bumps: a [compat] narrowing on a weakdep/test dep is not a public-API change. Co-Authored-By: Chris Rackauckas <accounts@chrisrackauckas.com>
Contributor
Author
|
Closing. Verified locally (ran the action's own downgrade.jl on the identical commit CI failed on) that raising the Mooncake compat floor does NOT fix the Downgrade lane. The failure is |
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.
Raises the Mooncake
[compat]floor to the latest (0.5.36) in every Project.toml that declares it, replacing theMooncake = "0.4.138, 0.5"union with a single floor. This is the "limit to latest Mooncake" fix for the promotion-caused DowngradeUnsatisfiablewall: the old union let the Downgrade min-resolution pin an ancient Mooncake (verified: master pins 0.5.15), whose promotion into the merged test env is what drove the Resolver.jl wall. A single floor at the latest stops the ancient pin.Raised floors
Project.toml(Optimization)0.4.138, 0.50.5.36lib/OptimizationBase/Project.toml0.4.138, 0.50.5.36Patch version bumps: Optimization
5.6.2 -> 5.6.3, OptimizationBase5.1.4 -> 5.1.5(a [compat] narrowing on a weakdep/test dep is not a public-API change).Verification (resolves_at_min = TRUE)
Ran the actual
julia-actions/julia-downgrade-compat@v2downgrade.jl(merged-extras resolution via Resolver.jl--min=@deps) on Julia 1.12, same skip list CI uses (stdlibs +SymbolicAnalysis+[sources]):Optimization(merged extras, Mooncake promoted to a full dep):Successfully resolved minimal versions— Mooncake pinned to exactly 0.5.36. NoUnsatisfiable.lib/OptimizationBase(Mooncake weakdep, merged extras):Successfully resolved minimal versions. NoUnsatisfiable.So the floor-raise alone resolves the min-resolution here; the Resolver-capacity wall (#52) does not persist for these projects after the bump.
Ignore until reviewed by @ChrisRackauckas.