Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

metadata updates #33

Closed
blairham opened this issue Jan 15, 2016 · 5 comments
Closed

metadata updates #33

blairham opened this issue Jan 15, 2016 · 5 comments

Comments

@blairham
Copy link

When you bump the vault version in the attributes, is it at all possible to bump the last number in your cookbook version in your metadata?

This is extremely important for berks and version locking.

@sh9189
Copy link
Contributor

sh9189 commented Feb 16, 2016

Yes, we do bump the cookbook version (major/minor/patch) before the cookbook is released to supermarket. You can see the latest release 1.5.0 bumped up the minor version.

@johnbellone
Copy link
Contributor

@blairham Are you deploying directly from this repository?

@blairham
Copy link
Author

@johnbellone I do

@johnbellone
Copy link
Contributor

Alright, I agree that we should be bumping the release of the cookbook each time that its updated inside of the attributes. That is generally the case. But there are times you're going to hit a lag time between the actual tag/release. The best way to do this would be to get your releases from the Chef Supermarket.

@lock
Copy link

lock bot commented May 19, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators May 19, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants