Net4x.PublishNuget 1.0.0.26324

dotnet add package Net4x.PublishNuget --version 1.0.0.26324
                    
NuGet\Install-Package Net4x.PublishNuget -Version 1.0.0.26324
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Net4x.PublishNuget" Version="1.0.0.26324" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="Net4x.PublishNuget" Version="1.0.0.26324" />
                    
Directory.Packages.props
<PackageReference Include="Net4x.PublishNuget" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add Net4x.PublishNuget --version 1.0.0.26324
                    
#r "nuget: Net4x.PublishNuget, 1.0.0.26324"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package Net4x.PublishNuget@1.0.0.26324
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=Net4x.PublishNuget&version=1.0.0.26324
                    
Install as a Cake Addin
#tool nuget:?package=Net4x.PublishNuget&version=1.0.0.26324
                    
Install as a Cake Tool

PublishNuget

Pushes every recent .nupkg/.snupkg of a folder to nuget.org through the website (a visible Chromium window, no API key), then waits until each pushed package is downloadable from the feed and deletes its local files.

Input Meaning
argument 1 / PACKAGE_DIRECTORY Folder holding the packages (default: Packages next to the executable).
argument 2 / NUGET_AVAILABILITY_TIMEOUT_MINUTES How long to wait for availability, 0 = no deadline (default: 30).
NUGET_USERNAME Microsoft account sign-in email (not the nuget.org profile name).
NUGET_PASSWORD Password of that account.
prompt (30s timeout) Age in hours of the files to push (default: 24).

Availability is checked every 30 seconds on the package content resource, so unlisted packages are detected too. A symbol package is deleted with its package: the feed exposes no availability of its own for it. Exit code is 1 when the deadline elapses with packages still missing, or when the sign-in at start fails; their files are kept. A push that fails is reported (Failed to push, reason on stderr) and its file is kept, but it does NOT change the exit code, unlike a sign-in failure at start. This includes a sign-in that fails in the middle of the run (the remaining pushes fail the same way) and the gallery's metadata conflict ("Package versions that differ only by metadata cannot be uploaded"), which is a failure, not an already-pushed package.

Sign-in

  • A visible Chromium window signs in at start, before the first upload, typing NUGET_USERNAME/NUGET_PASSWORD once each per sign-in (a sign-in repeated after the session expired types them again), only on Microsoft sign-in pages. A wrong password is never retried: fix it in the window.
  • Two-factor and any other extra step are completed by hand in the window (waits up to 10 minutes).
  • The session is saved to %LOCALAPPDATA%\UnpublishNuGet\nuget-session.json and reused (the variables are not needed while it is valid). It holds sign-in cookies: delete it to sign out.
  • Chromium is installed automatically on first run (Playwright). The window closes before the availability wait.
  • A package that already exists on nuget.org counts as pushed (as --skip-duplicate did); one that only differs by metadata from the existing version does not.
  • Throttled answers (Retry-After/429) are waited out, at most 20 retries per file, then the push fails.

Concurrent runs

The gallery has one upload slot per account: starting an upload cancels the in-progress upload of another process on the same account. Concurrent PublishNuget runs on one account therefore make each other's pushes fail (never publish wrong content; the failed files are kept and can be pushed again). Run one at a time. The shared session file is still replaced atomically.

There are no supported framework assets in this package.

Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
1.0.0.26324 0 11/20/2026
1.0.0.26322 80 11/18/2026
1.0.0.26319 94 11/15/2026
1.0.0.26315 90 11/11/2026
1.0.0.26311 92 11/7/2026
1.0.0.26309 96 11/4/2026
1.0.0.26308 91 11/3/2026
1.0.0.26304 101 10/30/2026
1.0.0.26303 109 10/30/2026
1.0.0.26292 99 10/19/2026
1.0.0.26288 94 10/15/2026
1.0.0.26281 99 10/8/2026
1.0.0.26273 106 9/30/2026
1.0.0.26271 102 9/28/2026
1.0.0.26270 105 9/27/2026
1.0.0.26269 106 9/26/2026
1.0.0.26268 107 9/25/2026
1.0.0.26267 111 9/24/2026
1.0.0.26265 112 9/22/2026
1.0.0.26264 120 9/20/2026
Loading failed