Skip to content

[RELEASE] v2.0.0 #681

Closed
Closed

Description

@github-actions

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.

Steps

  • Proposal validated: stable 2.0.0, supervised
  • Resolves from General alone (REL4)
  • Release PR opened, the gate passed locally — Project.toml, CHANGELOG.md, BREAKING.md
  • Checks green (release.jl ready): CI, documentation, breakage, the gate
  • Release PR merged
  • Tag and GitHub release; documentation of the tag
  • Registered in General
  • Issue closed

Activity

  1. github-actions commented on Nov 13, 2026

    @github-actions
    ContributorAuthor

    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

    What the agent will do

    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 covered 1.1.1-beta: ExaModels 0.12.
    • ✅ Proposal validated: stable 2.0.0, supervised
    • ✅ Resolves from General alone (REL4)
    • Release PR opened, the gate passed locally — Project.toml, CHANGELOG.md, BREAKING.md
    • Checks green (release.jl ready): CI, documentation, breakage, the gate
    • Release PR merged
    • Tag and GitHub release; documentation of the tag
    • Registered in General
    • Issue closed
  2. ct-release commented on Nov 13, 2026

    @ct-release
    Contributor

    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.

    • ✅ Proposal validated: stable 2.0.0, supervised
    • ✅ Resolves from General alone (REL4)
    • ✅ Release PR opened, the gate passed locally — Project.toml, CHANGELOG.md, BREAKING.md — chore: prepare CTDirect v2.0.0 release #682
    • Checks green (release.jl ready): CI, documentation, breakage, the gate
    • Release PR merged
    • Tag and GitHub release; documentation of the tag
    • Registered in General
    • Issue closed
  3. github-actions commented on Nov 13, 2026

    @github-actions
    ContributorAuthor

    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
    • ✅ Breakage.yml, run 43496268925: 7 job(s) passed
    • ✅ CI.yml, runs 43496275235, 43496281280, 43512396033: 16 job(s) passed
    • ✅ DocPreviewCleanup.yml, run 43496244307: 1 job(s) passed
    • ✅ Documentation.yml, run 43496264100: 4 job(s) passed
    • ✅ Labels.yml, run 43512379674: 1 job(s) passed
    • ✅ ReleaseGate.yml, run 43512385233: 1 job(s) passed
    • ✅ SpellCheck.yml, run 43496245388: 1 job(s) passed
    • ✅ Proposal validated: stable 2.0.0, supervised
    • ✅ Resolves from General alone (REL4)
    • ✅ Release PR opened, the gate passed locally — Project.toml, CHANGELOG.md, BREAKING.md — chore: prepare CTDirect v2.0.0 release #682
    • ✅ Checks green (release.jl ready): CI, documentation, breakage, the gate
    • Release PR merged
    • Tag and GitHub release; documentation of the tag
    • Registered in General
    • Issue closed
  4. github-actions commented on Nov 13, 2026

    @github-actions
    ContributorAuthor

    Phase 5 — Release PR merged.
    Done: #682 merged as fceb460.
    Decisions: none.
    Check: release.jl status: merged.
    Next: the Release tag workflow tags fceb460 and creates the GitHub release.

    • ✅ Proposal validated: stable 2.0.0, supervised
    • ✅ Resolves from General alone (REL4)
    • ✅ Release PR opened, the gate passed locally — Project.toml, CHANGELOG.md, BREAKING.md — chore: prepare CTDirect v2.0.0 release #682
    • ✅ Checks green (release.jl ready): CI, documentation, breakage, the gate
    • ✅ Release PR merged — fceb460
    • Tag and GitHub release; documentation of the tag
    • Registered in General
    • Issue closed
  5. github-actions commented on Nov 13, 2026

    @github-actions
    ContributorAuthor

    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.

  6. ocots commented on Nov 13, 2026

    @ocots
    Member

    @JuliaRegistrator register

    Release notes:

    🐛 Bug Fixes

    • 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.

    What's Changed

    New Contributors

    Full Changelog: v1.0.12...v2.0.0

  7. JuliaRegistrator commented on Nov 13, 2026

    @JuliaRegistrator

    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:

    git tag -a v2.0.0 -m "<description of version>" fceb4605a88d536c2a4fde6da519f8a3c1ed8f7f
    git push origin v2.0.0
    
  8. github-actions commented on Nov 13, 2026

    @github-actions
    ContributorAuthor

    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.

  9. github-actions commented on Nov 13, 2026

    @github-actions
    ContributorAuthor

    Phase 8 — CTDirect v2.0.0 is released.

    Left as is: nothing.
    Follow-ups: the downstream [compat] bumps, which CompatHelper opens.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    releaseRelease preparation

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions