Skip to content
This repository was archived by the owner on Jan 15, 2024. It is now read-only.

Releases: customink/strainer

v3.4.0

Choose a tag to compare

@sethvargo sethvargo released this 27 Apr 14:22
  • Add support for Berkshelf 3

v3.3.0

Choose a tag to compare

@sethvargo sethvargo released this 19 Aug 17:10
  • Don't use colored output on Windows by default

    Adds a dependency on Buff::Platform.

  • Don't use PTY on Windows

    Platforms that support PTY will sync output, but Windows will get blobs of output instead.

v3.2.2

Choose a tag to compare

@sethvargo sethvargo released this 14 Aug 15:01
  • Copy .cane and .kitchen.yml files into the sandbox

v3.2.1

Choose a tag to compare

@sethvargo sethvargo released this 08 Aug 14:43
  • Return true/false from Strainer#run and refactor success reporting to make Strainer more library-like (@wingrunr21)
  • Add --color and --no-color option to disable colored output (@wingrunr21)

v3.1.1

Choose a tag to compare

@sethvargo sethvargo released this 26 Jul 16:22
  • Added "Apache 2.0" license to gemspec (#33)

v3.1.0

Choose a tag to compare

@sethvargo sethvargo released this 26 Jul 14:24
  • Logically decide which commands are run inside the cookbook and which are run inside the sandbox (#31)

    Certain commands should be run from inside a cookbook (like RSpec and Test Kitchen), but others must be run in the sandbox (Knife and Foodcritic). This change attempts to intelligently detect what command the user wants and execute that command in the correct context.

  • Throw a fatal error when 'strainer test' is called on a chef_repo with no arguments

    Potentially a CI bug, if strainer test is called with no arguments on a chef_repo, the build would be marked as passing (when in reality, nothing was tested). This change does not affect cookbook_repos.

  • Various README updates

v3.0.5

Choose a tag to compare

@sethvargo sethvargo released this 20 Jul 20:08
  • Fix issue with Strainer::VERSION not being loaded

  • Remove autoload in favor of require_relative for Window's folks

    One of the main problems experienced with threading is that Kernel.autoload is not threadsafe. It also provides no time benefits on Windows. Switching to require_relative increases the overall load time (by about 0.03s in benchmarking), but reduces loadtime on Windows by 2 seconds. As an added benefit, the code is now threadsafe.

v3.0.4

Choose a tag to compare

@sethvargo sethvargo released this 20 Jul 20:08
  • Add Thor and Rake tasks

v3.0.3

Choose a tag to compare

@sethvargo sethvargo released this 20 Jul 20:07
  • (ignore this)

v3.0.2

Choose a tag to compare

@sethvargo sethvargo released this 20 Jul 20:07
  • Output summary message