Skip to content

Add allowPackageConflicts support to DotNetCoreCLI@2#21917

Open
GABRIELNGBTUC wants to merge 2 commits intomicrosoft:masterfrom
GABRIELNGBTUC:master
Open

Add allowPackageConflicts support to DotNetCoreCLI@2#21917
GABRIELNGBTUC wants to merge 2 commits intomicrosoft:masterfrom
GABRIELNGBTUC:master

Conversation

@GABRIELNGBTUC
Copy link

@GABRIELNGBTUC GABRIELNGBTUC commented Mar 10, 2026

  • Add --skip-duplicate support (allowPackageConflicts) to DotNetCoreCLIV2 push command

Context

Describe the context or motivation for this PR. Include links to any related Azure DevOps Work Items or GitHub issues.
📌 How to link to ADO Work Items

Today, the recommended way to use the nuget CLI is to use the command "dotnet nuget" since it is cross-platform and no longer requires "mono". A lot of the parameters from the NugetCommand@2 have a 1:1 match in DotNetCoreCLI@2, however the ability to skip duplicates and avoid errors when receiving a 429 Conflict is missing. This pull request aim at allowing to use the parameter allowPackageConflicts in DotNetCoreCLI@2

#20981


Task Name

DotNetCoreCLI@2


Description

Update the task DotNetCoreCLI@2 to allow the use of the parameter allowPackageConflicts from NugetCommand@2 when using DotNetCoreCLI@2 with push as the command


Risk Assessment (Low / Medium / High)

Low


Change Behind Feature Flag (Yes / No)

No as the risk is low. However, it could be if required.


Tech Design / Approach

  • Design has been written and reviewed.
  • Any architectural decisions, trade-offs, and alternatives are captured.

Documentation Changes Required (Yes/No)

Yes.

https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/reference/dotnet-core-cli-v2?view=azure-pipelines


Unit Tests Added or Updated (Yes / No)

Yes


Additional Testing Performed

List all other tests performed (manual or automated, including integration, regression, scenario tests, etc.).


Logging Added/Updated (Yes/No)

No logging was added.


Telemetry Added/Updated (Yes/No)

No telemetry was added.


Rollback Scenario and Process (Yes/No)

No rollback scenario was planned.


Dependency Impact Assessed and Regression Tested (Yes/No)

No dependency were changed


Checklist

  • Related issue linked (if applicable)
  • Task version was bumped — see versioning guide
  • Verified the task behaves as expected

…eCLIV2 push command (#2)

* Add --skip-duplicate support (allowPackageConflicts) to DotNetCoreCLIV2 push command

Co-authored-by: GABRIELNGBTUC <132353744+GABRIELNGBTUC@users.noreply.github.com>
---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: GABRIELNGBTUC <132353744+GABRIELNGBTUC@users.noreply.github.com>
@GABRIELNGBTUC GABRIELNGBTUC requested review from a team and tarunramsinghani as code owners March 10, 2026 14:41
@GABRIELNGBTUC GABRIELNGBTUC changed the title Add allowPackageConflicts / --skip-duplicate support to DotNetCor… Add allowPackageConflicts support to DotNetCoreCLI@2 Mar 10, 2026
@GABRIELNGBTUC GABRIELNGBTUC marked this pull request as draft March 10, 2026 14:41
@GABRIELNGBTUC GABRIELNGBTUC marked this pull request as ready for review March 10, 2026 14:55
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.

2 participants