I saw a strange behavior where a negut package from a skipped step was downloaded. I’m running version 126.96.36.1996.
Steps to reproduce…
- Have two steps that use two different nuget packages.
- Have one of the steps environments section setup to not include the environment you are deploying too.
- Select the step that is in the environment you are deploying too and skip the other step.
- Execute the deploy.
- Look at the logs for when it acquires the packages and you’ll see that it gets both packages even when you skipped the other step.
Not a common setup, but I ran across this by accident when I selected the wrong environment for one of our steps.