You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Release of CTDirect v2.0.0 (stable), requested in .releases/v2.0.0.toml and validated by ocots; run by the Release workflow of CTActions, following ct-agents/recipes/release.md. Progress is in the comments below, one per phase; each one repeats the steps, marked as far as they went.
Phase 2 — Tracking issue.
Done: the tracking issue, from the request.
Decisions: stable 2.0.0, supervised, validated by ocots; started by ocots. Versions applied: ct-agents v0.5.0, ct-conventions v0.13.0, CTActions a9f0450.
Check: release.jl request → the request is complete (expected version, a verdict for every candidate).
Next: the release PR, once the CI of main is green on 0b308c6866b38cb191360c96c4d35ec24762a560, after an approval of the environment release.
The proposal
Release proposal — CTDirect v2.0.0 (stable)
Version. Last release 1.1.8-beta; last version in General 1.0.12. Since 1.0.12: breaking changes, in 1.1.0-beta (the discretization API follows the CTSolvers dispatch contract) and 1.1.1-beta (1-D state, control and variable reach user functions as scalars). By REL1 (X ≥ 1: the breaking component is X) and REL2 (the triple must be above every one released, betas included), the version is 2.0.0. Jump in General (REL3). none. Resolves from General alone (REL4). ✅. Versions applied. ct-agents v0.5.0, ct-conventions v0.13.0, CTActions a9f0450 (the release tool).
What changes since 1.0.12
Breaking: the discretization API (1.1.0-beta) and the 1-D scalars (1.1.1-beta), with their BREAKING.md entries.
Enhancement: the path and boundary duals are given to CTModels by label.
Dependencies: CTModels 0.21.1, CTSolvers 0.7, CTParser 0.9.6, CTBase 0.30, ExaModels 0.12; the GPU bounds keep the newest major. With CTSolvers 0.7 the sign of the costate and duals of a maximisation problem changes (near-breaking, BREAKING.md).
The Release workflow does phases 2 to 8: the tracking issue [RELEASE] v2.0.0, the PR release/v2.0.0 after the gate, the checks, the tag, the registration, the close.
What you will do
Approve each privileged job (PR, merge, registration) on the run of Release.yml.
Give the go before the registration comment.
Validated: 2.0.0, supervised, by the Release workflow.
The review of the candidates
Candidate
Verdict
Note
pr-601: #601 refactor(DOCP): implement the CTSolvers dispatch contract — touches Project.toml, docs, src; not cited in the changelog since v1.0.12
covered
1.1.0-beta: the discretization API follows the CTSolvers dispatch contract (💥).
pr-614: #614 Add shape probe: measure "1-D = scalar" boundary compliance — touches src; not cited in the changelog since v1.0.12
covered
1.1.1-beta: 1-D state, control and variable passed as scalars (💥).
pr-622: #622 Deps bump for 1.1.1-beta: CTParser 0.9, CTModels 0.18, ExaModels 0.12; kkt→occidata runner — touches Project.toml, docs, src; not cited in the changelog since v1.0.12
covered
1.1.1-beta and 1.1.3-beta: dependency bumps and typed exceptions.
pr-635: #635 1.1.7-beta — touches src; not cited in the changelog since v1.0.12
added
GPU bounds and import → using (#617, #625) added to Refactoring and Dependencies of the release entry; 1.1.7-beta and 1.1.8-beta had no entry.
pr-643: #643 ci(docs): gate preview pushes behind label — touches docs; not cited in the changelog since v1.0.12
not-user-facing
Documentation workflow: preview pushes gated behind a label; no change to the content of the documentation.
pr-647: #647 chore(compat): drop [compat] specifiers no supported Julia version selects — touches Project.toml, docs; not cited in the changelog since v1.0.12
added
The compat specifiers dropped are the older GPU bounds, now said in the Dependencies entry (#625).
pr-677: #677 chore: compat CTModels 0.21, CTSolvers 0.7, CTParser 0.9.6 — touches Project.toml; not cited in the changelog since v1.0.12
covered
Dependencies entry of [Unreleased]: CTModels 0.21, CTSolvers 0.7, CTParser 0.9.6.
pr-680: #680 fix: give the path and boundary duals by label; unknown with :exa — touches Project.toml, src; not cited in the changelog since v1.0.12
covered
Bug Fixes and Enhancements of [Unreleased]; near-breaking notes in BREAKING.md.
dep-CTBase: CTBase: absent → deps
covered
CTBase is a direct dependency since 1.1.0-beta.
dep-CTParser: CTParser: absent → deps
covered
CTParser is a direct dependency since 1.1.1-beta (0.9.0-beta), now 0.9.6 in General.
compat-CTBase: [compat] of CTBase: none → 0.30
covered
1.1.0-beta / 1.1.1-beta; stays at 0.30 (Dependencies entry).
compat-CTModels: [compat] of CTModels: 0.10 → 0.21.1
covered
Dependencies entry of [Unreleased], and the betas.
compat-CTParser: [compat] of CTParser: none → 0.9.6
covered
Dependencies entry of [Unreleased].
compat-CTSolvers: [compat] of CTSolvers: 0.4 → 0.7
covered
Dependencies entry of [Unreleased], with the sign change of the max duals in BREAKING.md.
compat-ExaModels: [compat] of ExaModels: 0.9 → 0.12
Phase 3 — Release PR.
Done: #682: Project.toml, CHANGELOG.md, BREAKING.md and the request, with its run labels.
Decisions: none.
Check: release.jl gate → ready.
Next: the checks of #682.
Phase 4 — Checks of #682.
Done: every check the release needs ran and passed on the head commit 1c682150f5c78dfc54e8b67bd3f56d5c2b3cbefd.
Decisions: none.
Check: release.jl ready → ready.
Next: the merge job waits for your approval: open this run, Review deployments, tick release, Approve and deploy; it then merges with release.jl merge.
release.jl ready
✅ up to date with main
✅ AddToProject.yml, run 43496245108: 1 job(s) passed
✅ AutoAssign.yml, run 43496245432: 1 job(s) passed
Phase 6 — Tag and GitHub release.
Done: v2.0.0 is on fceb460, with its GitHub release.
Decisions: none.
Check: release.jl status: the tag is on the merge commit, the release is not a pre-release.
Next: the registration comment, once, after your approval: open this run, Review deployments, tick release, Approve and deploy.
With the :exa modeler, dual(sol, ocp, :label) of a path or boundary constraint returned 0, a value nobody computed: the :exa getter does not return these multipliers yet
(CTParser.jl#414). They are
now unknown: dual throws a PreconditionError whose message says so, and points to the :adnlp modeler (#672).
🛠 Enhancements
The path and boundary duals are given to CTModels.build_solution by label
(duals=Dict(label => value)), no longer by position: a solve no longer prints the
deprecation warning of CTModels 0.21.1. The duals read with dual(sol, ocp, :label) are
unchanged with :adnlp (#672).
🔄 Refactoring
import is replaced by using in src/ (#617); no change for callers.
🧪 Testing
test/ci/test_duals.jl: the duals by label with :adnlp (path labels of one and two
rows, boundary labels), no deprecation warning, the unknown duals of :exa, and the
backend-agnostic figure of an :exa solution with its path constraints.
Release workflows: ReleaseGate.yml (the gate of a release PR, REL1–REL7) and ReleaseTag.yml (tag and GitHub release of a merged release PR) call CTActions; Breakage.yml moves to breakage-suite.yml (one report, the REL1 check of a release
PR) and also runs on push to main; Documentation.yml accepts workflow_dispatch.
📚 Documentation
ct-conventions pinned at 0.5.0 in AGENTS.md (read from a git-ignored clone in .conventions/); AGENTS.md cites rules by identifier, CLAUDE.md redirects to it, and
the references to the former Handbook become rule identifiers. One .markdownlint.json
(GEN2) replaces the markdownlint-disable MD024 comment of this changelog (CHG2).
ct-conventions pinned at v0.7.0 in AGENTS.md: the release rules REL1–REL7 in the
index, and a Recurring tasks section pointing to the release recipe of ct-agents.
ct-agents pinned at v0.2.0 and ct-conventions at v0.7.1 in AGENTS.md: the recipes (the
release) are read from a git-ignored clone in .ct-agents/ at that tag, not from main
of ct-agents, and the proposal of a release states the versions applied. The clone of the
conventions is now .ct-conventions/ (it was .conventions/), like .ct-agents/.
ct-agents pinned at v0.3.0 in AGENTS.md: at the close of a release the agent runs release.jl audit, which checks the trail the release left.
ct-conventions pinned at v0.13.0 and ct-agents at v0.5.0 in AGENTS.md; the Release workflow of CTActions is called from .github/workflows/Release.yml.
📦 Dependencies
The bounds of the GPU packages keep only the newest major
(#625): CUDA 6, CUDSS 0.8,
MadNLP 0.10, MadNLPGPU 0.10.
[compat] moves to the current releases of the ecosystem, all in General: CTModels 0.19 → 0.21, CTSolvers 0.5 → 0.7, CTParser 0.9 → 0.9.6 (the first CTParser 0.9 in General). CTBase stays at 0.30.
CTModels lower bound 0.21.1: the first version that takes the duals by label.
With CTSolvers 0.7, the multipliers of a maximisation problem follow the convention of
the equivalent minimisation (min f and max -f give the same costate and duals): the
costate, the path duals and the boundary duals of a max problem change sign. A min
problem is unchanged. CTDirect passes the multipliers on as they are; the change comes from
CTSolvers (BREAKING.md of CTSolvers, v0.7.0).
✅ Compatibility
First stable release of the 1.1 line. Breaking relative to 1.0.12, through 1.1.0-beta and 1.1.1-beta (see their entries
and BREAKING.md); this entry itself adds no breaking change: the public API
is unchanged. Two near-breaking changes, see BREAKING.md: the sign of the costate and of the path and boundary duals of a
maximisation problem (CTSolvers 0.7), and, with :exa, the dual of a path or boundary
label throwing instead of returning a wrong 0.
Phase 7 — Registered in General.
Done: General holds 2.0.0 — JuliaRegistries/General#176155, merged.
Decisions: none.
Check: release.jl status: the registered tree is the tree of the tag.
Next: the final comment, then the issue is closed.
Activity
github-actions commentedon Nov 13, 2026
Phase 2 — Tracking issue.
Done: the tracking issue, from the request.
Decisions: stable
2.0.0, supervised, validated byocots; started byocots. Versions applied: ct-agentsv0.5.0, ct-conventionsv0.13.0, CTActionsa9f0450.Check:
release.jl request→ the request is complete (expected version, a verdict for every candidate).Next: the release PR, once the CI of
mainis green on0b308c6866b38cb191360c96c4d35ec24762a560, after an approval of the environmentrelease.The proposal
Release proposal — CTDirect v2.0.0 (stable)
Version. Last release
1.1.8-beta; last version in General1.0.12. Since1.0.12: breaking changes, in1.1.0-beta(the discretization API follows the CTSolvers dispatch contract) and1.1.1-beta(1-D state, control and variable reach user functions as scalars). ByREL1(X ≥ 1: the breaking component is X) andREL2(the triple must be above every one released, betas included), the version is2.0.0.Jump in General (
REL3). none.Resolves from General alone (
REL4). ✅.Versions applied. ct-agents
v0.5.0, ct-conventionsv0.13.0, CTActionsa9f0450(the release tool).What changes since
1.0.121.1.0-beta) and the 1-D scalars (1.1.1-beta), with theirBREAKING.mdentries.:exa, the dual of a path or boundary label throws instead of returning a wrong0(Give the path and boundary duals to build_solution by label (CTModels 0.21.1) #672).BREAKING.md).[Unreleased]yet, added by the release PR: the GPU bounds (Tighten the GPU compat bounds: keep only the newest major #625) andimport→using(Enforce Handbook tenet 2:using, neverimport#617), shipped by1.1.7-beta.What the agent will do
The
Releaseworkflow does phases 2 to 8: the tracking issue[RELEASE] v2.0.0, the PRrelease/v2.0.0after the gate, the checks, the tag, the registration, the close.What you will do
Release.yml.Validated:
2.0.0,supervised, by theReleaseworkflow.The review of the candidates
pr-601: #601 refactor(DOCP): implement the CTSolvers dispatch contract — touches Project.toml, docs, src; not cited in the changelog sincev1.0.121.1.0-beta: the discretization API follows the CTSolvers dispatch contract (💥).pr-614: #614 Add shape probe: measure "1-D = scalar" boundary compliance — touches src; not cited in the changelog sincev1.0.121.1.1-beta: 1-D state, control and variable passed as scalars (💥).pr-622: #622 Deps bump for 1.1.1-beta: CTParser 0.9, CTModels 0.18, ExaModels 0.12; kkt→occidata runner — touches Project.toml, docs, src; not cited in the changelog sincev1.0.121.1.1-betaand1.1.3-beta: dependency bumps and typed exceptions.pr-635: #635 1.1.7-beta — touches src; not cited in the changelog sincev1.0.12import→using(#617, #625) added to Refactoring and Dependencies of the release entry; 1.1.7-beta and 1.1.8-beta had no entry.pr-643: #643 ci(docs): gate preview pushes behind label — touches docs; not cited in the changelog sincev1.0.12pr-647: #647 chore(compat): drop [compat] specifiers no supported Julia version selects — touches Project.toml, docs; not cited in the changelog sincev1.0.12pr-677: #677 chore: compat CTModels 0.21, CTSolvers 0.7, CTParser 0.9.6 — touches Project.toml; not cited in the changelog sincev1.0.12pr-680: #680 fix: give the path and boundary duals by label; unknown with :exa — touches Project.toml, src; not cited in the changelog sincev1.0.12dep-CTBase:CTBase: absent → deps1.1.0-beta.dep-CTParser:CTParser: absent → deps1.1.1-beta(0.9.0-beta), now 0.9.6 in General.compat-CTBase:[compat]ofCTBase:none→0.301.1.0-beta/1.1.1-beta; stays at 0.30 (Dependencies entry).compat-CTModels:[compat]ofCTModels:0.10→0.21.1compat-CTParser:[compat]ofCTParser:none→0.9.6compat-CTSolvers:[compat]ofCTSolvers:0.4→0.7compat-ExaModels:[compat]ofExaModels:0.9→0.121.1.1-beta: ExaModels 0.12.2.0.0, supervisedREL4)Project.toml,CHANGELOG.md,BREAKING.mdrelease.jl ready): CI, documentation, breakage, the gatect-release commentedon Nov 13, 2026
Phase 3 — Release PR.
Done: #682:
Project.toml,CHANGELOG.md,BREAKING.mdand the request, with its run labels.Decisions: none.
Check:
release.jl gate→ ready.Next: the checks of #682.
2.0.0, supervisedREL4)Project.toml,CHANGELOG.md,BREAKING.md— chore: prepare CTDirect v2.0.0 release #682release.jl ready): CI, documentation, breakage, the gategithub-actions commentedon Nov 13, 2026
Phase 4 — Checks of #682.
Done: every check the release needs ran and passed on the head commit
1c682150f5c78dfc54e8b67bd3f56d5c2b3cbefd.Decisions: none.
Check:
release.jl ready→ ready.Next: the merge job waits for your approval: open this run, Review deployments, tick
release, Approve and deploy; it then merges withrelease.jl merge.release.jl readymainAddToProject.yml, run 43496245108: 1 job(s) passedAutoAssign.yml, run 43496245432: 1 job(s) passedBreakage.yml, run 43496268925: 7 job(s) passedCI.yml, runs 43496275235, 43496281280, 43512396033: 16 job(s) passedDocPreviewCleanup.yml, run 43496244307: 1 job(s) passedDocumentation.yml, run 43496264100: 4 job(s) passedLabels.yml, run 43512379674: 1 job(s) passedReleaseGate.yml, run 43512385233: 1 job(s) passedSpellCheck.yml, run 43496245388: 1 job(s) passed2.0.0, supervisedREL4)Project.toml,CHANGELOG.md,BREAKING.md— chore: prepare CTDirect v2.0.0 release #682release.jl ready): CI, documentation, breakage, the gategithub-actions commentedon Nov 13, 2026
Phase 5 — Release PR merged.
Done: #682 merged as fceb460.
Decisions: none.
Check:
release.jl status: merged.Next: the
Release tagworkflow tags fceb460 and creates the GitHub release.2.0.0, supervisedREL4)Project.toml,CHANGELOG.md,BREAKING.md— chore: prepare CTDirect v2.0.0 release #682release.jl ready): CI, documentation, breakage, the gategithub-actions commentedon Nov 13, 2026
Phase 6 — Tag and GitHub release.
Done:
v2.0.0is on fceb460, with its GitHub release.Decisions: none.
Check:
release.jl status: the tag is on the merge commit, the release is not a pre-release.Next: the registration comment, once, after your approval: open this run, Review deployments, tick
release, Approve and deploy.2.0.0, supervisedREL4)Project.toml,CHANGELOG.md,BREAKING.md— chore: prepare CTDirect v2.0.0 release #682release.jl ready): CI, documentation, breakage, the gateocots commentedon Nov 13, 2026
@JuliaRegistrator register
Release notes:
🐛 Bug Fixes
:examodeler,dual(sol, ocp, :label)of a path or boundary constraint returned0, a value nobody computed: the:exagetter does not return these multipliers yet(CTParser.jl#414). They are
now unknown:
dualthrows aPreconditionErrorwhose message says so, and points to the:adnlpmodeler (#672).🛠 Enhancements
CTModels.build_solutionby label(
duals=Dict(label => value)), no longer by position: a solve no longer prints thedeprecation warning of CTModels 0.21.1. The duals read with
dual(sol, ocp, :label)areunchanged with
:adnlp(#672).🔄 Refactoring
importis replaced byusinginsrc/(#617); no change for callers.🧪 Testing
test/ci/test_duals.jl: the duals by label with:adnlp(path labels of one and tworows, boundary labels), no deprecation warning, the unknown duals of
:exa, and thebackend-agnostic figure of an
:exasolution with its path constraints.Release workflows:
ReleaseGate.yml(the gate of a release PR,REL1–REL7) andReleaseTag.yml(tag and GitHub release of a merged release PR) call CTActions;Breakage.ymlmoves tobreakage-suite.yml(one report, theREL1check of a releasePR) and also runs on push to
main;Documentation.ymlacceptsworkflow_dispatch.📚 Documentation
AGENTS.md(read from a git-ignored clone in.conventions/);AGENTS.mdcites rules by identifier,CLAUDE.mdredirects to it, andthe references to the former Handbook become rule identifiers. One
.markdownlint.json(
GEN2) replaces themarkdownlint-disable MD024comment of this changelog (CHG2).v0.7.0inAGENTS.md: the release rulesREL1–REL7in theindex, and a Recurring tasks section pointing to the release recipe of ct-agents.
v0.2.0and ct-conventions atv0.7.1inAGENTS.md: the recipes (therelease) are read from a git-ignored clone in
.ct-agents/at that tag, not frommainof ct-agents, and the proposal of a release states the versions applied. The clone of the
conventions is now
.ct-conventions/(it was.conventions/), like.ct-agents/.v0.3.0inAGENTS.md: at the close of a release the agent runsrelease.jl audit, which checks the trail the release left.v0.13.0and ct-agents atv0.5.0inAGENTS.md; theReleaseworkflow of CTActions is called from.github/workflows/Release.yml.📦 Dependencies
(#625): CUDA
6, CUDSS0.8,MadNLP
0.10, MadNLPGPU0.10.[compat]moves to the current releases of the ecosystem, all in General: CTModels0.19→0.21, CTSolvers0.5→0.7, CTParser0.9→0.9.6(the first CTParser0.9in General). CTBase stays at0.30.0.21.1: the first version that takes the duals by label.0.7, the multipliers of a maximisation problem follow the convention ofthe equivalent minimisation (
min fandmax -fgive the same costate and duals): thecostate, the path duals and the boundary duals of a
maxproblem change sign. Aminproblem is unchanged. CTDirect passes the multipliers on as they are; the change comes from
CTSolvers (BREAKING.md of CTSolvers, v0.7.0).
✅ Compatibility
1.0.12, through1.1.0-betaand1.1.1-beta(see their entriesand BREAKING.md); this entry itself adds no breaking change: the public API
is unchanged. Two near-breaking changes, see BREAKING.md: the sign of the costate and of the path and boundary duals of a
maximisation problem (CTSolvers 0.7), and, with
:exa, the dual of a path or boundarylabel throwing instead of returning a wrong
0.What's Changed
New Contributors
Full Changelog: v1.0.12...v2.0.0
JuliaRegistrator commentedon Nov 13, 2026
Registration pull request created: JuliaRegistries/General/176155
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
github-actions commentedon Nov 13, 2026
Phase 7 — Registered in General.
Done: General holds
2.0.0— JuliaRegistries/General#176155, merged.Decisions: none.
Check:
release.jl status: the registered tree is the tree of the tag.Next: the final comment, then the issue is closed.
2.0.0, supervisedREL4)Project.toml,CHANGELOG.md,BREAKING.md— chore: prepare CTDirect v2.0.0 release #682release.jl ready): CI, documentation, breakage, the gategithub-actions commentedon Nov 13, 2026
Phase 8 — CTDirect v2.0.0 is released.
2.0.0, supervisedREL4)Project.toml,CHANGELOG.md,BREAKING.md— chore: prepare CTDirect v2.0.0 release #682release.jl ready): CI, documentation, breakage, the gateLeft as is: nothing.
Follow-ups: the downstream
[compat]bumps, which CompatHelper opens.