Docs not clear about pushing beta software packages

[OlafHaag]

I want to make a package for beta software (franz messenger). Unfortunately the documentation is not clear about what exactly I'd have to do to mark package versions as prerelease when pushing to the official choco-user repository.

set the beta as a prerelease when pushing the item to chocolatey.org (CreatePackages)

But in the docs about pushing packages I can't find anything that would explain how to do this with the command line. Should I just extend the push command by -pre?

[ferventcoder]

Push doesn't need anything special.

You just need to version the package appropriately to be a prerelease.

[ferventcoder]

What should we add?

[OlafHaag]

Please add to the documentation what needs to be done and how to make clear to everyone, that a package version is for beta/prerelease software. I had the impression there was some switch that could prevent installing prerelease software in chocolatey.

You just need to version the package appropriately to be a prerelease.

So, for example, I just simply write »beta« or »pre« somewhere into the version? E.g. the official versioning for franz is currently »5.0.0-beta.15« Then a good place for information on versioning beta software would be here. Thanks.

[ferventcoder]

That's a good point. Lots of folks not familiar with nuget and semantic versioning may not see this.

For reference for you - <version>1.0.0-wordsnumbers</version> is all it takes to make a version a prerelease. The key is the - that denotes this is a prerelease that comes after the version number. So 5.0.0-beta.15 (if the dot is allowed, and 5.0.0-beta15 if not) would go into the version tag in the nuspec.