HISTORY.md in metric_fu-4.11.1 vs HISTORY.md in metric_fu-4.11.2

@@ -2,15 +2,22 @@
 
 Each change should fall into categories that would affect whether the release is major (breaking changes), minor (new behavior), or patch (bug fix). See [semver](http://semver.org/) and [pessimistic versioning](http://docs.rubygems.org/read/chapter/16#page74)
 
 As such, a _Feature_ would map to either major (breaking change) or minor. A _bug fix_ to a patch.  And _misc_ is either minor or patch, the difference being kind of fuzzy for the purposes of history.  Adding tests would be patch level.
 
-### Master [changes](https://github.com/metricfu/metric_fu/compare/v4.11.1...master)
+### Master [changes](https://github.com/metricfu/metric_fu/compare/v4.11.2...master)
 
 * Breaking Changes
 * Features
 * Fixes
 * Misc
+
+### [4.11.2](https://github.com/metricfu/metric_fu/compare/v4.11.1...v4.11.2)
+
+* Fixes
+  * Use reek as library, otherwise reek >= 1.6.2 hangs while reading input from stdin. (Martin Gotink, #240, fixes #239)
+* Misc
+  * Refactor MetricFu::Templates::MetricsTemplate#write into a composed method. (#237)
 
 ### [4.11.1](https://github.com/metricfu/metric_fu/compare/v4.11.0...v4.11.1)
 
 * Fixes
   * Captured shell-output now only includes STDOUT.  Appending STDERR was breaking expectations. (Benjamin Fleischer, #230, fixes #229)