I noticed it after an error in my script. My assembly versions were auto incrementing but it looks like they are not updated when there is a change in a content file. This leads OctoPack to create a package with duplicate version and push it NuGet server in Octopus. That doesn’t cause any error and Octopus uses the old package. I think it’s a bug.
Hi - thanks for the heads-up. Pushing an existing package version will fail in Octopus 2.4; in 2.3 we would expect the package to be overwritten, I’ve added an issue here to check it out: https://github.com/OctopusDeploy/Issues/issues/858