You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 14, 2021. It is now read-only.
Cookbooks uploaded to the new cookbook storage API can have extended SemVer version numbers with prerelease sections, like 1.0.0-dev
But specifying such a version in a Policyfile or the cookbook's metadata version gives me an error:
Installing codio_base = 3.3.1-dev from path
Error: Failed to generate Policyfile.lock
Reason: (Chef::Exceptions::InvalidCookbookVersion) '3.3.1-dev' does not match 'x.y.z' or 'x.y'
Are prerelease versions string currently supported? If so, how?
The text was updated successfully, but these errors were encountered:
joelmoss
changed the title
Prelease version strings?
Pre-release version strings?
Sep 1, 2015
Not yet. The Chef Server allows them, but chef-dk is re-using Chef's metadata.rb code, which disallows them. Also, it's likely that chef-client would barf when you attempted to run the cookbooks. It's definitely a thing we'd like to add, but I don't know when exactly it'll happen.
It says in the Policyfile README that:
But specifying such a version in a Policyfile or the cookbook's metadata version gives me an error:
Are prerelease versions string currently supported? If so, how?
The text was updated successfully, but these errors were encountered: