Does Octopus support semver 2.0 versions with metadata? I’ve tried to create a package with the git sha in the version metadata, but I’m getting the error:
The package version ‘1.0.0.21+2f052aba’ for ‘xxx’ returned from the package repository doesn’t match the requested package version ‘1.0.0.21’
The package is downloaded from an external (github) nuget feed.
I’m assuming that you’re running this on a Cloud instance, my instance is currently running Build 8275. If you want to check yours I can re-test if they’re on different builds.
Also, the calverp/grades repository I used in my test is public if you want to try testing with that too and see if you get a different result.
Hi Paul, one difference that I’ve noticed is that I’m not using the “GitHub Repository Feed” feed type, instead a generic “NuGet Feed” (Working with the NuGet registry - GitHub Docs).
I believe I have replicated the behaviour that you’re seeing, are you able to confirm that when you’re creating a release you see just the package version displayed without the metadata?
e.g.
I’m deploying the application to azure using a “DEPLOY AN AZURE APP SERVICE” step. Looks like this step is missing the option to change the download behavior.