Repository navigation
Publish the experimental .NET packages to NuGet - #575
Merged
Merged
Conversation
ludfjig
force-pushed
the
publish-dotnet-packages
branch
from
November 13, 2026 00:55
cab779f to
d3ad6d9
Compare
ludfjig
force-pushed
the
publish-dotnet-packages
branch
from
November 13, 2026 23:51
d3ad6d9 to
cfcd153
Compare
ludfjig
force-pushed
the
publish-dotnet-packages
branch
2 times, most recently
from
November 17, 2026 00:03
62c249f to
5df5371
Compare
ludfjig
force-pushed
the
publish-dotnet-packages
branch
2 times, most recently
from
November 17, 2026 19:33
10b1704 to
88efba5
Compare
ludfjig
force-pushed
the
publish-dotnet-packages
branch
from
November 17, 2026 20:44
88efba5 to
8dd3a7b
Compare
ludfjig
force-pushed
the
publish-dotnet-packages
branch
from
November 17, 2026 21:39
8dd3a7b to
2fed8ec
Compare
ludfjig
force-pushed
the
publish-dotnet-packages
branch
from
November 17, 2026 22:16
2fed8ec to
55aa446
Compare
simongdavies
previously approved these changes
Nov 18, 2026
simongdavies
left a comment
Member
There was a problem hiding this comment.
A couple of minor comments and questions:
Should we include some package metadata in the csproj files:
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
ludfjig
force-pushed
the
publish-dotnet-packages
branch
2 times, most recently
from
November 18, 2026 22:39
98d6abf to
5a2011b
Compare
ludfjig
force-pushed
the
publish-dotnet-packages
branch
2 times, most recently
from
November 19, 2026 18:49
1eb5abe to
e865afb
Compare
ludfjig
force-pushed
the
publish-dotnet-packages
branch
from
November 19, 2026 19:09
e865afb to
294bc69
Compare
ludfjig
force-pushed
the
publish-dotnet-packages
branch
2 times, most recently
from
November 19, 2026 20:00
c34a499 to
6de643d
Compare
ludfjig
force-pushed
the
publish-dotnet-packages
branch
2 times, most recently
from
November 19, 2026 22:13
d0b5b2a to
1f1e7d6
Compare
ludfjig
force-pushed
the
publish-dotnet-packages
branch
5 times, most recently
from
November 20, 2026 00:46
106b231 to
7df1914
Compare
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
force-pushed
the
publish-dotnet-packages
branch
from
November 20, 2026 01:16
7df1914 to
4315d86
Compare
jsturtevant
reviewed
Nov 20, 2026
jsturtevant
approved these changes
Nov 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
Hyperlight.WasmandHyperlight.Wasm.Buildpackages 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.ymland packs each by its exact path. Release branches push the packages and theHyperlight.Wasmsymbol package to NuGet with trusted publishing. Pushes to main attach them todev-latestas development builds of the next minor release, such as0.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.ymlin this repository and set theNUGET_USERrepository variable.The trusted publishing policy can require a GitHub environment, which limits who can publish. That needs
environment:onpublish-dotnetand can follow later.