A heavy amount of refactoring for DI (dependency injection) support was added to Arcade per dotnet/arcade#6672. Because of this, a lot of tasks were updated to use the DI because their dependencies were being refactored so that the MSBuild task that these tests were being built for could consume them through DI. PublishArtifactsInManifest was one of these tasks, and it should be refactored to follow better design patterns.
A heavy amount of refactoring for DI (dependency injection) support was added to Arcade per dotnet/arcade#6672. Because of this, a lot of tasks were updated to use the DI because their dependencies were being refactored so that the MSBuild task that these tests were being built for could consume them through DI. PublishArtifactsInManifest was one of these tasks, and it should be refactored to follow better design patterns.