Skip to content

feat: Begin transition from DevOps to GHA - #11

Open
BenjaminMichaelis wants to merge 9 commits into
Polyglossy:mainfrom
BenjaminMichaelis:main
Open

BenjaminMichaelis wants to merge 9 commits into
Polyglossy:mainfrom
BenjaminMichaelis:main

Conversation

@BenjaminMichaelis

@BenjaminMichaelis BenjaminMichaelis commented May 17, 2026 •

Copy link
Copy Markdown

WIP - some high level attempts at getting the GHA pipelines started

This pull request introduces a comprehensive overhaul of the project's CI/CD automation and dependency management. It adds new GitHub Actions workflows for continuous integration and publishing, establishes a composite action for standardized build and test steps across platforms, and sets up automated dependency updates for GitHub Actions, npm, and NuGet packages. These changes modernize and streamline the project's automation, making builds, tests, and releases more reliable and maintainable.

CI/CD Workflow Automation:

  • Introduced a new .github/workflows/ci.yml workflow to handle continuous integration on both Windows and Linux, including branch and path filters, artifact uploads, and improved concurrency handling.
  • Added a .github/workflows/publish.yml workflow to automate the release process, including building, testing, packaging, and publishing to NuGet, npm, and the VSCode Marketplace, with support for dry-run simulations and proper environment gating.

Reusable Build and Test Logic:

  • Created a composite GitHub Action at .github/actions/build-and-test/action.yml to encapsulate cross-platform build and test logic, including caching, environment setup, and platform-specific steps for both Windows and Linux.

Automated Dependency Management:

  • Added a .github/dependabot.yml configuration to enable Dependabot for GitHub Actions, npm, and NuGet, ensuring dependencies are kept up to date automatically with grouped updates and appropriate labeling.

Miscellaneous:

  • Minor whitespace cleanup in Directory.Build.targets.

@sassdawe

Copy link
Copy Markdown
Member

Hey @BenjaminMichaelis do you think we can try building without Arcade? I opted out of using it on my machine as Jon said that we actually don't need it as that was an internal requirement for the OG version, and seemingly I can build without it just fine.

…o-gha-plan

Migrate from Azure Pipelines to GitHub Actions
Consolidate CI build jobs with matrix strategy
…ching-simplification

Simplify npm caching in build-and-test action
…igate-failures

fix: resolve form input race and clean up GHA Arcade references
…peline-alignment

ci: align GHA pipeline parity with legacy behavior
…-non-ci-changes

chore: revert non-CI changes from main branch
@BenjaminMichaelis

Copy link
Copy Markdown
Author

@sassdawe totally forgot to mention, I can't trigger workflows so going a bit blind here, but I think we should review, then merge, and iterate on any issues we see. Thoughts? I am having the workflows run on my fork though - prior to the merge, the CI ran: https://github.com/BenjaminMichaelis/interactive/actions/runs/26665445807/job/78597690923

After the latest merge it looks like though it is failing: https://github.com/BenjaminMichaelis/interactive/actions/runs/29498556169/job/87621356663#step:4:194

@sassdawe

sassdawe commented Jul 16, 2026 via email

Copy link
Copy Markdown
Member

@sassdawe

Copy link
Copy Markdown
Member

After the latest merge it looks like though it is failing: https://github.com/BenjaminMichaelis/interactive/actions/runs/29498556169/job/87621356663#step:4:194

I totally broke the package-lock files when I was trying to reconcile the merge conflicts here: sassdawe#23

@sassdawe

Copy link
Copy Markdown
Member

@BenjaminMichaelis I am in the process of cherry picking these three files, so I can test them without anything else:

  • .github/actions/build-and-test/action.yml
  • .github/workflows/ci.yml
  • .github/workflows/publish.yml

I believe you'll need to create another branch with nothing else changed just these files and submit a PR from that branch.

@BenjaminMichaelis

Copy link
Copy Markdown
Author

@sassdawe I have just dropped the merge out of this pr!

@sassdawe

sassdawe commented Jul 19, 2026 •

Copy link
Copy Markdown
Member

@sassdawe I have just dropped the merge out of this pr!

I took your changes with minimal changes to produce cleaner history: FEAT: (GH Actions) CI and Release pipelines

@BenjaminMichaelis
BenjaminMichaelis marked this pull request as ready for review August 6, 2026 05:50
sassdawe added a commit that referenced this pull request Aug 21, 2026
Sync fork with Polyglossy/interactive main
…ce drift (#8)

* Make named-request header test independent of live httpbin.org

httpbin.org no longer returns a Server response header, so the test
failed deterministically. Use InterceptingHttpMessageHandler to supply the
Server header and assert it is forwarded in the later request.

* fix(tests): clear inherited MSBuild SDK vars so prebuild tests work on runners with newer SDKs

ubuntu-latest now ships the .NET 11 SDK. The prebuild tests run 'dotnet new' and
'dotnet build' outside the repo, which selects SDK 11 and generates net11.0 projects,
while 'dotnet test' exports MSBuildSDKsPath/MSBuildExtensionsPath for the repo-pinned
10.0 SDK to the test host. The mismatch fails with NETSDK1045. Clear the inherited
variables in the test assembly so child processes resolve their own SDK.

* fix(tests): pin prebuild SDK with global.json instead of clearing MSBuild env vars

Prebuild tests ran `dotnet new`/`dotnet build` under ~/.trydotnet/prebuilds, where no
global.json applies, so the newest installed SDK was chosen while the test host ran on the
SDK pinned by the repo. Route prebuilds to a test-owned directory (via the existing
TRYDOTNET_PREBUILDS_PATH override) that carries the repo's SDK pin, so children resolve the
same SDK as the host. This replaces the earlier approach of clearing MSBuildSDKsPath and
MSBuildExtensionsPath.

* fix(tests): make prebuild SDK pin setup robust to concurrent test processes

Key the prebuilds directory by a hash of the pin, write global.json atomically, and fall back
to the default prebuilds location on IO errors so a module initializer can never fail the test host.

* ci: run npm tests, upload build logs, strip symbols packages (legacy pipeline parity) (#9)

* ci: run npm ciTest suites and upload build binlogs for legacy parity

- Run 'npm run ciTest' for polyglot-notebooks, -browser, -vscode and
  -vscode-insiders after the .NET tests (if !cancelled()) on both runners.
- Upload artifacts/log/Release as <OS>-build-logs (14 day retention).
- Remove *.symbols.nupkg before the Windows packages upload.

* ci: shorten parity comments and link the files they reference

* ci: link legacy pipeline references to a pinned commit
* Upgrade Roslyn to 5.12.0 for C# 15 support

Roslyn 5.12.0 is the first stable release exposing LanguageVersion.CSharp15.
It requires System.* 10.0.10 packages, so the central pins for
Microsoft.Bcl.AsyncInterfaces, System.Collections.Immutable,
System.IO.Pipelines, System.Reflection.Metadata and System.Text.Json
are raised to match (NU1109 otherwise).

The C# kernel now reports language version 15.0, and tests cover C# 15
syntax that has no runtime dependency beyond net10.0.

* Align Microsoft.Extensions.Logging.Abstractions pin with Roslyn 5.12.0 requirement

* Derive kernel language version from Roslyn and tighten C# 15 diagnostics test
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants