Add version requirements for dotnet nuget push options

[Copilot]

The --configfile and --allow-insecure-connections options were documented as available in .NET 6 SDK and later, but these options were added in .NET 9 SDK (specifically 9.0.300) and .NET 10 SDK respectively.

Changes

• Added "Available since .NET 9 SDK" to --configfile option description
• Added "Available since .NET 10 SDK" to --allow-insecure-connections option description

Follows the version annotation pattern used in other .NET CLI documentation (e.g., dotnet-nuget-add-source.md, dotnet-build.md).

Original prompt

---

This section details on the original issue you should resolve

<issue_title>dotnet nuget push does not recognize the --configfile option in the .NET 8 SDK</issue_title>
<issue_description>### Type of issue

Outdated article

Description

The dotnet nuget push documentation states that it applies to .NET 6 SDK and later.
However, the --configfile option is not available in the .NET 8 SDK, despite this claim.

dotnet --version
8.0.417

dotnet nuget push --help



Usage: dotnet nuget push [arguments] [options]

Arguments:
  [root]  Specify the path to the package and your API key to push the package to the server.

Options:
  -h|--help                      Show help information
  --force-english-output         Forces the application to run using an invariant, English-based culture.
  -s|--source <source>           Package source (URL, UNC/folder path or package source name) to use. Defaults to DefaultPushSource if specified in NuGet.Config.
  -ss|--symbol-source <source>   Symbol server URL to use.
  -t|--timeout <timeout>         Timeout for pushing to a server in seconds. Defaults to 300 seconds (5 minutes).
  -k|--api-key <apiKey>          The API key for the server.
  -sk|--symbol-api-key <apiKey>  The API key for the symbol server.
  -d|--disable-buffering         Disable buffering when pushing to an HTTP(S) server to decrease memory usage.
  -n|--no-symbols                If a symbols package exists, it will not be pushed to a symbols server.
  --no-service-endpoint          Does not append "api/v2/package" to the source URL.
  --interactive                  Allow the command to block and require manual action for operations like authentication.
  --skip-duplicate               If a package and version already exists, skip it and continue with the next package in the push, if any.

dotnet --version
10.0.102

dotnet nuget push --help


Usage: dotnet nuget push [arguments] [options]

Arguments:
  [root]  Specify the path to the package and your API key to push the package to the server.

Options:
  -h|--help                      Show help information
  --force-english-output         Forces the application to run using an invariant, English-based culture.
  -s|--source <source>           Package source (URL, UNC/folder path or package source name) to use. Defaults to DefaultPushSource if specified in NuGet.Config.
  --allow-insecure-connections   Allows pushing to HTTP sources (insecure).
  -ss|--symbol-source <source>   Symbol server URL to use.
  -t|--timeout <timeout>         Timeout for pushing to a server in seconds. Defaults to 300 seconds (5 minutes).
  -k|--api-key <apiKey>          The API key for the server.
  -sk|--symbol-api-key <apiKey>  The API key for the symbol server.
  -d|--disable-buffering         Disable buffering when pushing to an HTTP(S) server to decrease memory usage.
  -n|--no-symbols                If a symbols package exists, it will not be pushed to a symbols server.
  --no-service-endpoint          Does not append "api/v2/package" to the source URL.
  --interactive                  Allow the command to block and require manual action for operations like authentication.
  --skip-duplicate               If a package and version already exists, skip it and continue with the next package in the push, if any.
  --configfile                   The NuGet configuration file. If specified, only the settings from this file will be used. If not specified, the hierarchy of configuration files from the current directory will be used. For more information, see https://docs.microsoft.com/nuget/consume-packages/configuring-nuget-behavior.

Page URL

https://learn.microsoft.com/de-de/dotnet/core/tools/dotnet-nuget-push

Content source URL

https://github.com/dotnet/docs/blob/main/docs/core/tools/dotnet-nuget-push.md

Document Version Independent Id

6fa9479a-85db-5498-6b7e-2418fc7bac32

Platform Id

bc44bd16-d795-3c01-de13-35660f66e5fa

Article author

@karann-msft

Metadata

• ID: b363ab07-ea19-574f-e0db-25fd5702255d
• PlatformId: bc44bd16-d795-3c01-de13-35660f66e5fa
• Service: dotnet-fundamentals

Related Issues

---

Associated WorkItem - 548270</issue_description>

Comments on the Issue (you are @copilot in this section)

@meaghanlewis It looks like the --configfile option was made available in .NET 9.0.3xx SDK: https://github.com/dotnet/sdk/pull/47126.

• Fixes dotnet nuget push does not recognize the --configfile option in the .NET 8 SDK #51312

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

---

Internal previews

📄 File	🔗 Preview link
docs/core/tools/dotnet-nuget-push.md	dotnet nuget push

[Copilot]

Pull request overview

This PR corrects the version requirements for two command-line options in the dotnet nuget push documentation. The issue reported that these options were incorrectly documented as available in .NET 6 SDK and later, when they were actually added in more recent SDK versions.

Changes:

• Added version availability information to the --configfile option (available since .NET 9 SDK)
• Added version availability information to the --allow-insecure-connections option (available since .NET 10 SDK)