Skip to content

Publish the experimental .NET packages to NuGet - #575

Merged
ludfjig merged 1 commit into
mainfrom
publish-dotnet-packages
Nov 20, 2026
Merged

ludfjig merged 1 commit into
mainfrom
publish-dotnet-packages

Conversation

@ludfjig

@ludfjig ludfjig commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

The Hyperlight.Wasm and Hyperlight.Wasm.Build packages from #564 are not published, and a local pack holds only the build machine's native library.

This builds the native libraries for linux-x64, win-x64 and osx-arm64 in CreateRelease.yml and packs each by its exact path. Release branches push the packages and the Hyperlight.Wasm symbol package to NuGet with trusted publishing. Pushes to main attach them to dev-latest as development builds of the next minor release, such as 0.17.0-dev.412. The release notes give the command that installs the matching AOT compiler.

Before the next release, a nuget.org admin for hyperlight-dev must add a trusted publishing policy for CreateRelease.yml in this repository and set the NUGET_USER repository variable.

The trusted publishing policy can require a GitHub environment, which limits who can publish. That needs environment: on publish-dotnet and can follow later.

@ludfjig ludfjig added the kind/enhancement New feature or request label Nov 13, 2026
@ludfjig
ludfjig added this pull request to stack #576 November 13, 2026 00:42
@ludfjig
ludfjig force-pushed the publish-dotnet-packages branch from cab779f to d3ad6d9 Compare November 13, 2026 00:55
@ludfjig
ludfjig force-pushed the publish-dotnet-packages branch from d3ad6d9 to cfcd153 Compare November 13, 2026 23:51
@ludfjig
ludfjig force-pushed the publish-dotnet-packages branch 2 times, most recently from 62c249f to 5df5371 Compare November 17, 2026 00:03
@ludfjig
ludfjig force-pushed the publish-dotnet-packages branch 2 times, most recently from 10b1704 to 88efba5 Compare November 17, 2026 19:33
@ludfjig
ludfjig force-pushed the publish-dotnet-packages branch from 88efba5 to 8dd3a7b Compare November 17, 2026 20:44
@ludfjig
ludfjig force-pushed the publish-dotnet-packages branch from 8dd3a7b to 2fed8ec Compare November 17, 2026 21:39
@ludfjig
ludfjig force-pushed the publish-dotnet-packages branch from 2fed8ec to 55aa446 Compare November 17, 2026 22:16
simongdavies
simongdavies previously approved these changes Nov 18, 2026

@simongdavies simongdavies left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A couple of minor comments and questions:

Should we include some package metadata in the csproj files:

https://learn.microsoft.com/en-us/nuget/create-packages/package-authoring-best-practices#package-metadata

Is there a reason not to publish macOs package?

Should we publish symbols? - https://learn.microsoft.com/en-us/nuget/create-packages/symbol-packages-snupkg

Comment thread .github/workflows/CreateRelease.yml Resolved
Comment thread .github/workflows/CreateRelease.yml Resolved
Comment thread .github/workflows/CreateRelease.yml Resolved
@ludfjig
ludfjig force-pushed the publish-dotnet-packages branch 2 times, most recently from 98d6abf to 5a2011b Compare November 18, 2026 22:39
@ludfjig
ludfjig force-pushed the publish-dotnet-packages branch 2 times, most recently from 1eb5abe to e865afb Compare November 19, 2026 18:49
@ludfjig
ludfjig force-pushed the publish-dotnet-packages branch from e865afb to 294bc69 Compare November 19, 2026 19:09
@ludfjig
ludfjig force-pushed the publish-dotnet-packages branch 2 times, most recently from c34a499 to 6de643d Compare November 19, 2026 20:00
@ludfjig
ludfjig force-pushed the publish-dotnet-packages branch 2 times, most recently from d0b5b2a to 1f1e7d6 Compare November 19, 2026 22:13
Base automatically changed from experimental-build-runtime to main November 19, 2026 23:53
@ludfjig
ludfjig force-pushed the publish-dotnet-packages branch 5 times, most recently from 106b231 to 7df1914 Compare November 20, 2026 00:46
Build the packages' native libraries for linux-x64, win-x64 and
osx-arm64 in the release workflow, and pack each by its exact path. The
Windows libraries link the C runtime statically, so they load without
the Visual C++ Redistributable.

Release branches push the packages and Hyperlight.Wasm's symbol
package to NuGet with trusted publishing. Main attaches them to the
dev-latest release when the run is for main's head, and its notes give
the commands that install the matching AOT compiler.

Release packages take hyperlight-wasm's version with the preview
suffix, and the branch name must match it. Builds from main are
versioned as development builds of the next minor release, such as
0.17.0-dev.412.

Signed-off-by: Ludvig Liljenberg <4257730+ludfjig@users.noreply.github.com>
@ludfjig
ludfjig force-pushed the publish-dotnet-packages branch from 7df1914 to 4315d86 Compare November 20, 2026 01:16
Comment thread .github/workflows/CreateRelease.yml Resolved
@ludfjig
ludfjig merged commit 92ccbd1 into main Nov 20, 2026
55 checks passed
@ludfjig
ludfjig deleted the publish-dotnet-packages branch November 20, 2026 17:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

kind/enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants