Skip to content

Confirm Terminal.Gui v2 build & test suite pass in CI (.NET 10) #1

Closed

Description

@tig

Tracks workstream A / checklist item 2 in PLAN.md.

The Terminal.Gui v2 modernization from ConsoleGuiTools#267 is landed on main/develop (Terminal.Gui 2.1.0, new window classes, xUnit suite, module 1.0.0). We need a known-green baseline before building further.

Tasks

  • Ensure the .NET 10 SDK is available to CI (see global.json).
  • dotnet build the solution clean.
  • Run the xUnit suite under test/ and confirm green.
  • Basic GitHub Actions workflow running build + tests on push/PR (precursor to the full release pipeline — see the CI/CD migration issue).

Blocks the rebrand and release work.

Activity

  1. tig commented on Jun 23, 2026

    @tig
    MemberAuthor

    ✅ Confirmed — known-green .NET 10 baseline

    The CI Tests workflow now runs Invoke-Build Build, Test, Package and is green on all three OSes:

    OS Build xUnit Package
    windows-latest ✅ ✅ ✅
    macos-latest ✅ ✅ ✅
    ubuntu-latest ✅ ✅ ✅
    • Build: dotnet build GraphicalTools.slnx -c Release → 0 errors (6 pre-existing nullable/analyzer warnings).
    • Tests: xUnit suite under test/ → Passed: 78, Failed: 0, Skipped: 0.
    • SDK: setup-dotnet now pins to global.json (.NET 10.0.102) via global-json-file (CI: confirm .NET 10 build + xUnit suite green (#1) #10), so CI builds/tests against the intended SDK.

    Tasks

    • Ensure the .NET 10 SDK is available to CI (via global.json) — now explicit
    • dotnet build the solution clean
    • Run the xUnit suite under test/ and confirm green (78/78)
    • Basic GitHub Actions workflow running build + tests on push/PR

    PLAN.md workstream A / item 2 checked off in 91974df.

    Note (follow-up)

    The first run saw a transient 504 Gateway Time-out from PSGallery while installPSResources.ps1 fetched platyPS on Windows — an infra flake, not a code issue; a re-run was green. Worth adding a small install-retry to tools/installPSResources.ps1 to harden CI against PSGallery hiccups (tracked separately under the CI/CD pipeline work, not blocking this baseline).

  2. added 2 commits that reference this issue on Jun 27, 2026
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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions