Repository navigation
chore: compat CTModels 0.21, CTSolvers 0.7, CTParser 0.9.6 - #677
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
This was referenced Nov 13, 2026
ocots
marked this pull request as ready for review
November 13, 2026 15:44
Closed
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.
Summary
Moves
[compat]to the current releases of the CT ecosystem, so that CTDirect resolves with the CTParser release published on 2026-11-12. No source change.0.300.300.190.210.50.70.90.9.60.9in General)Every bound is satisfied by a release in General (
REL4). ExaModels stays at0.12, which CTParser requires.Conventions applied: ct-conventions v0.13.0, ct-agents v0.5.0.
To check before leaving draft
BREAKING.md). CTDirect passesstats.multipliers*toCTModels.build_solutionas is, so the costate and duals of a maximisation problem may change sign. To confirm on an example, and to record inBREAKING.mdif it does.path_constraints_dual/boundary_constraints_dualused insrc/DOCP_data.jl. They still work, with a warning. Moving toduals=is left for another PR.The harmonization of #642 (labels, templates, lint configuration) goes in separate PRs, one per theme.
🤖 Generated with Claude Code