dotnet-nuget-update-source(1)

💖 dotnet-nuget-update-source(1) 💖

okay bestie, welcome to the dotnet-nuget-update-source page from the .NET Documentation manual — yes that's the manual name, we're not gatekeeping it 💅

This article applies to: ✔️ .NET 6 SDK and later versions

⚠️ Real talk before anything else: Use package sources that you trust. No cap. 🫶

---

✨ NAME ✨

dotnet-nuget-update-source — Update a NuGet source. 🌸

---

🎀 SYNOPSIS 🎀

dotnet nuget update source <NAME> [--source <SOURCE>] [--username <USER>]
    [--password <PASSWORD>] [--store-password-in-clear-text]
    [--valid-authentication-types <TYPES>] [--configfile <FILE>]

dotnet nuget update source -h|--help

---

🦋 DESCRIPTION 🦋

So the dotnet nuget update source command updates an existing source in your NuGet configuration files. That's the whole vibe. It's not creating a new one, it's not deleting one — it's updating one, the way you update your profile pic but for package sources. Iconic. ✨

---

🍓 ARGUMENTS 🍓

• NAME — Name of the source. Just the name, bestie, that's all it needs. 💜

---

💅 OPTIONS 💅

• --configfile <FILE> — The NuGet configuration file (nuget.config) to use. If you specify it, then only the settings from this file will be used — like, it's the only one invited to the party. If you don't specify it, the hierarchy of configuration files from the current directory will be used instead. For more information, see Common NuGet Configurations. 🎀
• -p, --password <PASSWORD> — Password to be used when connecting to an authenticated source. 🔐

Be aware that encrypted passwords are only supported on Windows. Moreover, they can only be decrypted on the same machine and by the same user who originally encrypted them. So no, your friend's laptop is not gonna decrypt your secrets, and honestly? Neither is your future self on a new machine. 💀

• -s, --source <SOURCE> — Path to the package source. Simple. Clean. Main character energy. 🌈
• --store-password-in-clear-text — Enables storing portable package source credentials by disabling password encryption.

WARNING: Storing passwords in clear text is strongly discouraged. Like, strongly. For more information on managing credentials securely, refer to the security best practices for consuming packages from private feeds. Please don't do the clear text thing unless you truly have to, bestie 😭

• -u, --username <USER> — Username to be used when connecting to an authenticated source. 🌸
• --valid-authentication-types <TYPES> — Comma-separated list of valid authentication types for this source. Set this to basic if the server advertises NTLM or Negotiate and your credentials must be sent using the Basic mechanism — for instance when using a PAT with on-premises Azure DevOps Server. Other valid values include negotiate, kerberos, ntlm, and digest, but these values are unlikely to be useful. iykyk. 🧚

---

🔥 EXAMPLES 🔥

• Update a source with name of mySource:

dotnet nuget update source mySource --source c:\packages

slay. That's it, that's the example. ✨

---

👑 SEE ALSO 👑

• Security best practices for managing package source credentials
• Package source sections in NuGet.config files
• sources command (nuget.exe)

---

k bye bestie, go forth and update those sources responsibly 💖

This was the dotnet-nuget-update-source(1) page, dated 2025-10-30 — and that's the version and date, so we're done here. 🎀✨🦋