Commit ea4c5d2e authored by Tim Smith's avatar Tim Smith

Release 1.0.0

Signed-off-by: default avatarTim Smith <tsmith@chef.io>
parent 8a96c798
......@@ -2,23 +2,25 @@
This file is used to list changes made in each version of ulimit.
## 0.6.0
- Rewrote as new style custom resource
## 0.5.0
- Added a Test Kitchen config for basic testing
## 1.0.0
- Breaking change: This cookbook now requires Chef 12.7 or later
- LWRPs converted to custom resources with Chef 13 compatibility
- Added the rtprio property to the user resource
- Updated the cookbook to not append .conf onto filenames when the user already specified a name that ends in .conf
- Added a chefignore file to limit what files get uploaded to the chef server
- Added a Test Kitchen config + InSpec tests for unit testing
- Added the license file to the repo to resolve a Foodcritic warning
- Added a Berksfile
- Added a chefignore file to limit what gets uploaded to the Chef Server
- Resolved all cookstyle warnings
- Added Chefspec matchers
- Fixed the metadata license string to be an SPDX standard license string to resolve Foodcritic warnings
- Add supports, source_url, issues_url, and chef_version metadata to resolve Foodcritic warnings
- Resolved backwards compatibility check for Chef 10
- Switched the default recipe from platform to platform_family to catch more Debian/Ubuntu derivatives
- Added testing with ChefDK's delivery local mode in Travis
- Expanded the readme with better information on requirements and usage examples
- Removed ChefSpec matchers that are autogenerated by ChefSpec now
- Added Cookstyle and autocorrected all code
- Added a basic ChefSpec unit test
## 0.3.2
......
......@@ -4,7 +4,7 @@ maintainer_email 'bmhatfield@gmail.com'
license 'Apache-2.0'
description 'Resources for manaing ulimits'
long_description IO.read(File.join(File.dirname(__FILE__), 'README.md'))
version '0.5.0'
version '1.0.0'
%w(amazon centos redhat scientific oracle fedora debian ubuntu).each do |os|
supports os
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment