delta/ruby-gems/chef.git/tasks, branch https_shell github.com: opscode/chef.git Use the `changelog` namespace for Rake tasks 2016-11-09T18:59:09+00:00 Tom Duffield tom@chef.io 2016-11-07T19:57:54+00:00 f84b6352a347b823b82d2c5f8e3e3905d6948221 Signed-off-by: Tom Duffield <tom@chef.io> 
Signed-off-by: Tom Duffield <tom@chef.io>
Add gem release badge to the readme / changelog header (#5527) 2016-11-08T18:47:09+00:00 Tim Smith tsmith@chef.io 2016-11-08T18:47:09+00:00 8b71d8d8b5358d7c85a466c1f32d6f268e823df0 When we update our changelog it’s a bit confusing since multiple days go by before we ship the new release. Adding a header to the changelog and a readme gem release badge should help clear up what our current release actually is. Signed-off-by: Tim Smith <tsmith@chef.io> 
When we update our changelog it’s a bit confusing since multiple days go by before we ship the new release. Adding a header to the changelog and a readme gem release badge should help clear up what our current release actually is.

Signed-off-by: Tim Smith <tsmith@chef.io>
 Update changelog generator to better fill our pattern (#5515) 2016-11-04T16:19:32+00:00 Tom Duffield tom@chef.io 2016-11-04T16:19:32+00:00 87d5ca4a6d20f895e844672aa44b17a8ce3560af * Update changelog generator to better fill our pattern Configure the changelog generator to better fit our current pattern of changelogs. By utilizing the HISTORY.md file, we can generate a combined changelog of the latest version from HISTORY.md to now. Then, when we cut a release we can simply move our current changelog into HISTORY.md (using the appropriate rake task) and start the process over again. This might even be a first step to having the Chef Versioner generate the changelog automatically for us each time it bumps the version, and then we just need to groom it as we go along. Signed-off-by: Tom Duffield <tom@chef.io> * Add HISTORY.md for the 12.15.19 release Signed-off-by: Tom Duffield <tom@chef.io> 
* Update changelog generator to better fill our pattern

Configure the changelog generator to better fit our current pattern of
changelogs. By utilizing the HISTORY.md file, we can generate a combined
changelog of the latest version from HISTORY.md to now. Then, when we
cut a release we can simply move our current changelog into
HISTORY.md (using the appropriate rake task) and start the process over
again.

This might even be a first step to having the Chef Versioner generate
the changelog automatically for us each time it bumps the version, and
then we just need to groom it as we go along.

Signed-off-by: Tom Duffield <tom@chef.io>

* Add HISTORY.md for the 12.15.19 release

Signed-off-by: Tom Duffield <tom@chef.io>
Merge pull request #5225 from chef/bundle_lock_fix 2016-08-23T01:42:00+00:00 Matt Wrock matt@mattwrock.com 2016-08-23T01:42:00+00:00 c5e387c5c5e7e3d94986eb7384bc7d8a7058b014 Add monkey patch to fix bundle locks for platforms 
Add monkey patch to fix bundle locks for platforms
 add monkey patch to fix bundle locks for platforms 2016-08-19T04:17:38+00:00 Matt Wrock matt@mattwrock.com 2016-08-19T04:17:38+00:00 8bdf04d9a52b416e7d39090cf315c05e1bc537cb 






fix Style/BlockDelimiters, Style/MultilineBlockLayout and 0.42.0 engine upgrade
2016-08-17T20:25:02+00:00

Lamont Granquist
lamont@scriptkiddie.org

2016-08-17T19:15:26+00:00

a0c32511bc6634538374ca4b433032b8acd05f96

Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>





Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>







Add release notes and gem version diff generator
2016-08-10T21:50:44+00:00

John Keiser
john@johnkeiser.com

2016-08-08T18:31:54+00:00

9860fd5e3edbda739670a2d24ccb1c9845a0cbf1












Change recommended by @jkeiser to make single gem updates work correctly.
2016-08-03T01:35:15+00:00

Noah Kantrowitz
noah@coderanger.net

2016-08-03T01:35:15+00:00

008ab141fa55b30524e04ff9dbd1368a9165bef4












Making rake:dependencies work
2016-06-15T16:10:53+00:00

tyler-ball
tyleraball@gmail.com

2016-06-14T17:31:08+00:00

5581377922587f6e83221e4a8b4795cbf4a8cd87












fix delete in bundle-platform
2016-05-26T00:59:43+00:00

Matt Wrock
matt@mattwrock.com

2016-05-26T00:59:43+00:00

68120b524128c539604604b0eea296fda4c35305