Jesse Houwing

@copilot in your analysis **ONLY** look at v5 tasks and v5 common. The v4 tasks are there purely for backwards compatibility mode and are expected to be removed. See: https://github.com/microsoft/azure-devops-extension-tasks/pull/1490

@copilot check whether you added my last request to drop v4 in all your analysis.

@copilot analyze whether the `tmp` npm package can truly be replaces by native `fs`. The package us used specifically to address security concerns about the predictability of the `temp` folder...

@copilot the dependency size report still shows 0B for all tasks. This cannot be true. Ensure all builds & cleanup logic is executed prior to calculating the size per task.

@copilot based on the new data on which dependencies the project depends on, the biggest advantage can be made by reducing the shared dependencies across all tasks (since those are...

@copilot also, why is the PublishExtension almost 12MB larger than most other extensions, which dependencies contribute to that size increase. And there are a few tasks that don't depend on...

My bandwidth to fix this is currently low and I personally do not have any clients that use this feature anymore as far as I am aware. I suspect the...

Possible solution avenues: 1. Download the nuget for client I object model 16 and commit it to the task folder. 1. Remove `latest` from the call to vswhere and offer...

Initial fix just pushed out. Not detecting VS2026.

No it doesn't detect 2026, it explicitly ignores it. That version has shipped. If it finds vs2022 or lower it will try to use that I'm working on a version...