yes this is the feature I’m trying to use. When the tasks package version is different to the website package then it just throws an error on Acquire packages
The step failed: Activity failed with error ‘The package tasks could not be located in the built-in repository.’.
In the project settings I have ‘Use the Version number from an included package’ set to the website package. Maybe this is interfering with fetching the step package.
Yes that parameter will set the value for all packages. If you want to specify different versions for different packages you can use --package=stepName:PackageVersion as shown in the below doc about Octo.exe which is the same thing that the TeamCity plugin uses in the background: