actions-marketplace-validations/Publish NuGet

Build, Pack & Publish a NuGet package with dotnet core on project version change

Trust Signals

workflow.ymlSHA-pinned

uses: actions-marketplace-validations/b3b00_publish-nuget@ba68b6ac80abc518cb8eedf5f3ba5dbe069c457f # no releases — HEAD as of 2026-07-13

tags can be moved; commit SHAs can't. why a SHA?

name	description	required	default
PROJECT_FILE_PATH	Filepath of the project to be packaged, relative to root of repository	yes	—
BUILD_CONFIGURATION	Configuration to build and package (default is Release)	no	Release
BUILD_PLATFORM	Platform target to compile (default is empty/AnyCPU)	no	—
NUSPEC_FILE	file path to nuspec file	no	—
PACKAGE_NAME	NuGet package id, used for version detection & defaults to project name	no	—
VERSION_FILE_PATH	Filepath with version info, relative to root of repository & defaults to PROJECT_FILE_PATH	no	—
VERSION_REGEX	Regex pattern to extract version info in a capturing group	no	^\s<(Package\|)Version>(.)<\/(Package\|)Version>\s*$
VERSION_STATIC	Useful with external providers like Nerdbank.GitVersioning, ignores VERSION_FILE_PATH & VERSION_REGEX	no	—
TAG_COMMIT	Flag to toggle git tagging, enabled by default	no	true
TAG_FORMAT	Format of the git tag, [*] gets replaced with actual version	no	v*
NUGET_KEY	API key to authenticate with NuGet server	no	—
NUGET_SOURCE	NuGet server uri hosting the packages, defaults to https://api.nuget.org	no	https://api.nuget.org
INCLUDE_SYMBOLS	Flag to toggle pushing symbols along with nuget package to the server, disabled by default	no	false

name	description
VERSION	Version of the associated git tag
PACKAGE_NAME	Name of the NuGet package generated
PACKAGE_PATH	Path to the generated NuGet package
SYMBOLS_PACKAGE_NAME	Name of the symbols package generated
SYMBOLS_PACKAGE_PATH	Path to the generated symbols package