This is the Changelog for the Stove gem.
v7.1.6 (2020-01-29)
v7.1.5 (2019-10-18)
- Use the latest expeditor config and fix buildkite tests #148 (tas50)
- Add gem/buildkite badges and add Ruby 2.3 testing #149 (tas50)
- Add github templates, contributing doc, and update license template #152 (tas50)
- Switch back to depending on chef-api #153 (tas50)
- Release as chef-stove
- Removed support for Ruby 2.2 as it is now a end of life Ruby release.
- Unpinned the bundler development dependency
- Added back missing templates files that were necessary for error messages
- The metadata.rb file will now be included in uploads to match the behavior of berkshelf 7+
- The bindir is once again included in the files list in the gemspec
- The yank command has been removed as this command causes large downstream impact to other users and should not be part of the tooling
- Resolve the missing stove binary in 6.1.0
- The number of files shipped in the stove gem has been reduced to reduce on disk installation size. If you need the full set of development files you'll need to checkout the gem from Github.
- All references to the Community site have been renamed to Supermarket. This includes the name of the
communityplugin and allCommunityclasses references within the code. This should not be a breaking change unless your developing against stove as a library. - The long ago deprecated
bakecommand has been removed.
- Git tagging errors now include more useful error messaging.
- The help command now better describes
--no-gitand--endpointflags. - For developers running stove from the git repository, the application now properly loads stove from the repository instead of from an installed gem.
- Support for uploading to Artifactory
- Match Chef's metadata behavior with chef_version and ohai_version to allow version constraints like '>= 12.5', '< 14'
- Allow having gem version in cookbook metadata.json
- Better align gem version logic with how Chef handles it
- Enable pushing extended metadata for Chef 12 by default
- Add gem metadata to the extended metadata whitelist
- Use git porcelain vs. -s to avoid having local git configs interfere with stove functionality
- Only populate the extended metadata if the fields are actually present in the metadata
- Support for Ruby 2.0 has been dropped as Ruby 2.0 has been EOL'd
- Don't delete the metadata.json file if there isn't a metadata.rb
- Support uploading cookbooks to Supermarket that lack a metadata.rb, but have a metadata.json
- This version of stove now requires Ruby 2.0 or later
- Add endpoint config to the .stove config file for users of private Supermarkets
- Add option --no-ssl-verify to skip SSL verification
- Add chef_version and ohai_version metadata when extended-metadata is enabled
- Add CONTRIBUTING.md, MAINTAINERS.md and .foodcritic to the file whitelist
- Use chef.io instead of getchef.com
- Ignore
vendor/directory - Do not publish extended metadata fields like
issues_urlandsource_urlby default (GH-64, GH-72). These fields can be optionally added using the new--extended-metadataflag. - Add support for Ruby 2.2
- Use binmode when reading and writing the tgz (GH-64)
- Include new metadata methods for Supermarket
- Fix a bug with line endings when generating tarballs
- Add support for
issues_urlandsource_urlmetadata attributes
- Only upload fully-compiled metadata (i.e. only upload metadata.json, not metadata.rb)
- Fix a bug where files beginning with a dot (
.) were not packaged
- Fix a critical bug where nested directories are flattened
This version has been removed from Rubygems
- Add the ability to "yank" (delete) a cookbook from the Supermarket
- Remove the
--categoryflag (it is no longer honored) - Fix a bug where the
resources/folder was not uploaded - Fix a bug when the cookbook name is not the same as the metdata name in the uploaded tarball
This version has been removed from Rubygems
- Use the generated tempfile directly (instead of writing to disk and creating File objects)
- Add a default version constraint ('>= 0.0.0')
- Only package Ruby files under
recipes/and similar directories - Dynamically generate the metadata.json in memory (save disk IO)
- Use Rubygem's TarWrtier instead of minitar (removed dependency)
- Bump version of Chef API to support tempfile IO objects
- Add support for signed git tags
- Require Ruby 1.9+
- Remove i18n in favor of ERB
- Remove solve gem
- Remove GitHub functionality
- Remove JIRA functionality
- Remove bump and devodd functionality
- Clear up confusion on Gemfile vs not Gemfile
- Always read tarball objects as binary
- End tempfiles in the correct extension (needed to detect mime_types)
- Bump required version of ChefAPI gem
- Remove unused errors and code
- Improved documentation
- Remove editor files (
.swp, etc) before packaging - Upgrade to RSpec 3
- Improve test coverage
- Publish to Supermarket by default
- Completely refactor the runner for speed optimizations
- Introduce a new configuration file format
- Add i18n support
- Add Filters and validations that execute before any commands are run
- Autoload plugins and actions
- Improve help output by grouping options
- Trap Signal interrupts cleanly
- Remove formatters
- Switch to logify
- Introduce significantly more logging and log levels
- Remove HTTParty & Jiralicious in favor or Faraday
- Improve rake task to automatically perfom a minor bump when no version if given
- Persist data across the cookbook object
- Use singleton classes to save memory and loadtime
- Check if the git remote is in sync with local branch before pushing
- Add support for bumping devodd releases
- Add a custom rake task
- Add ability to publish GitHub releases
- Fix CLI bug that didn't allow options to parse
- Add logging during release process
- Fix error where the community site does not give an adequate response
- Retry uploads 3 times in case the community site is being lame
- Fix a bug where
--log-levelwas being ignored
- Initial release