Raise Mooncake compat floor to 0.5.36 (fix Downgrade resolution)#1526
Closed
ChrisRackauckas-Claude wants to merge 1 commit into
Closed
Raise Mooncake compat floor to 0.5.36 (fix Downgrade resolution)#1526ChrisRackauckas-Claude wants to merge 1 commit into
ChrisRackauckas-Claude wants to merge 1 commit into
Conversation
Narrow the Mooncake [compat] floor to the latest release (0.5.36) in every Project.toml that declares Mooncake compat, so the strict downgrade min-resolution stops pinning an ancient Mooncake. Both the root package env and the docs env are updated. Verified on Julia 1.12 with julia-actions/julia-downgrade-compat@v2 (merged-extras path, mode=deps, --min=@deps): Mooncake is promoted weakdep->dep and Resolver.jl resolves successfully at minimum versions, pinning Mooncake 0.5.36 (no Unsatisfiable). 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
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 release (0.5.36) in everyProject.tomlthat declares Mooncake compat, so the strict Downgrade min-resolution stops pinning an ancient Mooncake ("limit to latest Mooncake" fix for the promotion-caused DowngradeUnsatisfiablewall).Raised floors
Project.toml(root,[compat])0.5.250.5.36docs/Project.toml([compat])0.50.5.36Root package version bumped
7.113.0->7.113.1(a[compat]narrowing on a weakdep is a patch-level change). No[deps]/[weakdeps]/[extras]UUID lines were touched.Verification (resolves_at_min = true)
Reproduced the downgrade min-resolution faithfully on Julia 1.12 with
julia-actions/julia-downgrade-compat@v2, the exact path the centralizedDowngrade.ymltakes: the root has[extras]+[targets].test, sodowngrade.jlruns the merged-extras resolution withmode=deps,--min=@deps,allow_reresolve=falsesemantics. In that path Mooncake is promoted weakdep -> dependency ([ Info: Promoting Mooncake from weakdep to dependency in merged project) and fed to Resolver.jl.Result with the raised floor:
Resolver.jl resolved successfully at minimum versions (exit 0, no
Unsatisfiable), pinningMooncake = 0.5.36in the emittedManifest.toml. Soresolves_at_min = true— the floor-raise alone is sufficient here; the Resolver-capacity wall does not persist at current master.(Control run with the old
0.5.25floor also resolves at current registry state, pinning Mooncake 0.5.25 — so this change does not regress resolution and correctly lifts the floor to the latest.)Ignore until reviewed by @ChrisRackauckas.
🤖 Generated with Claude Code