[Manodasan Wignarajah (manodasanW)]

Adds a lightweight GitHub Actions product build reusing build.cmd without building the full test suite.

• Builds Release product binaries for x86, x64, and ARM64 and uploads a combined CsWinRT NuGet package.
• Runs on all PRs, pushes to  staging/3.0 , and manual dispatch. PRs and staging pushes run UnitTest under both JIT and Native AOT; manual runs provide a single opt-in checkbox.
• Includes precompiled SDK/XAML implementation projections on staging pushes, with an option for manual runs.
• Uploads a separate  TestProjections.

Validation

• Local JIT/AOT UnitTest runs each passed 796 tests, with five skipped.
• Tested downloaded CI NuGet and projection artifacts with both SDK reference DLLs replaced in an isolated targeting-pack cache. SDK/XAML consumption, component authoring, third-party projection generation/packing, and JIT/AOT execution passed.
• Native component activation passed on .NET 10 with the existing workaround and on .NET 11 without it.

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[Dongle (dongle-the-gadget)]

If possible, can you add a workflow to build the Microsoft.Windows.SDK.NET.Ref package as well?

[Manodasan Wignarajah (manodasanW)]

If possible, can you add a workflow to build the Microsoft.Windows.SDK.NET.Ref package as well?

I will need to see what can be done. Building the exact package is a bit less trivial as that is built elsewhere today with the other SDK packages. I probably can easily generate the ref assembly which someone can patch the package with. But given with CsWinRT 3.0, this is now a ref assembly with just the public API surface, I expect that we won't need to change that much for most changes as it would be the implementation that is changing which can be generated as part of the app build.

[Dongle (dongle-the-gadget)]

Another comment: can you have the CI run on push as well? I noticed that there are commits that are not associated with a PR. In addition, it is possible for PRs to be merged without synchronizing with the staging/3.0 branch, which leads to CI runs on that PR to not incorporate new changes.

[Manodasan Wignarajah (manodasanW)]

can you have the CI run on push as well? I noticed that there are commits that are not associated with a PR.

Dongle (@dongle-the-gadget) do you mean branches that PRs haven't been created for yet (i.e. work in progress that isn't ready for PR yet)?

In addition, it is possible for PRs to be merged without synchronizing with the staging/3.0 branch, which leads to CI runs on that PR to not incorporate new changes

If we have the action run daily on staging/3.0 (assuming there is changes), will that address this concern? That way the build for the PR is just for validating that and not to get what staging/3.0 has.

[Dongle (dongle-the-gadget)]

we have the action run daily on staging/3.0 (assuming there is changes), will that address this concern

Yeah this is what I meant, have the CI run on staging/3.0 on a regular basis, or when there are new commits pushed to the staging/3.0 branch.