chore(deps): update dependency enumerableasyncprocessor to v3

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
EnumerableAsyncProcessor	nuget	major	2.1.111 -> 3.0.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[claude]

Claude finished @thomhurst's task —— View job

---

PR Review: EnumerableAsyncProcessor v3.0.0 Update

Todo List

• Examine the changed file (Directory.Packages.props)
• Search codebase for EnumerableAsyncProcessor usage
• Check for potential breaking changes from v2 → v3 major update
• Assess build and test compatibility
• Provide comprehensive review feedback

---

Review Feedback

✅ Code Quality & Best Practices

The dependency update is clean and follows proper centralized package management using Directory.Packages.props. The change is minimal and isolated.

⚠️ Potential Issues & Breaking Changes

This is a major version update (v2.1.111 → v3.0.0), which typically indicates breaking changes. Based on my analysis:

Usage Location: TUnit.Pipeline/Modules/UploadToNuGetModule.cs:42-48

return await nupkgs.SelectAsync(file =>
        context.DotNet().Nuget.Push(new DotNetNugetPushOptions(file)
        {
            Source = "https://api.nuget.org/v3/index.json",
            ApiKey = options.Value.ApiKey
        }, cancellationToken), cancellationToken: cancellationToken)
    .ProcessOneAtATime();

Concerns:

1. API Changes: Major version bumps often include method signature changes, renamed methods, or removed functionality
2. Extension Method Changes: The code uses SelectAsync() and ProcessOneAtATime() extension methods - these may have changed signatures or behavior
3. Namespace Changes: The using EnumerableAsyncProcessor.Extensions; import may need updates

🚨 Build Compatibility

• Cannot verify build success due to .NET SDK version mismatch (requires 9.0.304, only 8.0.118 available)
• Recommendation: Ensure CI/CD builds pass before merging

🔒 Security Considerations

• No immediate security concerns with this dependency update
• EnumerableAsyncProcessor is from the same author (@thomhurst) as this repository, reducing supply chain risk

🧪 Test Coverage

• The affected code is in TUnit.Pipeline (build/deployment pipeline)
• Recommendation: Run pipeline tests to ensure NuGet upload functionality still works correctly

Recommendations

1. ⚠️ High Priority: Verify the build succeeds with the new version before merging
2. 📋 Test Pipeline: Run a test deployment to ensure the NuGet upload process works
3. 📖 Check Changelog: Review EnumerableAsyncProcessor v3.0.0 release notes for breaking changes
4. 🔄 Consider: If breaking changes exist, update the usage accordingly

Risk Assessment

Medium Risk - While usage is limited to one location, it's in a critical build pipeline component, and major version updates often contain breaking changes.