Skip to content

Add a trusted-publishing workflow for NuGet.org - #2

Merged
AlyxSharkBite merged 1 commit into
mainfrom
ci/nuget-publish
Sep 1, 2026
Merged

AlyxSharkBite merged 1 commit into
mainfrom
ci/nuget-publish

Conversation

@AlyxSharkBite

Copy link
Copy Markdown
Owner

Ports PkLibSharp's publish.yml (renamed throughout, and the licence-check comment corrected from MIT/PKLib to GPL/LZO), and fixes the package metadata before the first push bakes it in permanently:

  • PackageProjectUrl now points at this repository instead of upstream LZO — NuGet renders it as "Project website".
  • The description leads with the GPL-2.0-or-later consequence so it is visible on the gallery page.
  • Adds explicit RepositoryUrl and package tags.

Verified locally: dotnet pack produces a nuspec with the corrected projectUrl, repository, tags, and description.

Publishing stays gated: the workflow only fires on a published release, and then waits on the release environment's required reviewer.

🤖 Generated with Claude Code

publish.yml pushes the exact assets attached to a published GitHub release
to NuGet.org, authenticated by trusted publishing (OIDC) against a policy
scoped to this repository, this workflow file and the `release`
environment. Two human gates stand in front of the irreversible push:
publishing the release, and approving the environment.

The csproj pointed PackageProjectUrl at upstream LZO, which NuGet renders
as "Project website"; it now points at this repository, with upstream
attribution staying in the description and README. The description leads
with the GPL-2.0-or-later consequence so it is visible on the gallery page
rather than only behind the license link, and the package gains explicit
RepositoryUrl and tags.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@AlyxSharkBite
AlyxSharkBite merged commit 8554a2b into main Sep 1, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant