Autobumper: com.timgroup:tim-slogger_2.12:0.1.1069 -> com.timgroup:tim-slogger_2.12:0.1.1070, com.timgroup:tim-slogger_2.11:0.1.1069 -> com.timgroup:tim-slogger_2.11:0.1.1070  * changes to com.timgroup:tim-slogger_2.12:    * autobumper: Autobumper: com.timgroup:tim-logger:0.5-20170406-143535 -> com.timgroup:tim-logger:1.5.1073        * changes to com.timgroup:tim-logger:          * Graham Allan: gallan: bump major version to trump version I accidentally published locally.             Ensure version number from a local "gradle upload" doesn't accidentally beat what's uploaded by CI.          * Graham Allan: gallan: create an appender suitable for consumption by filebeat.             With zero configuration it:              - separates json by newlines, as required by Filebeat              - rolls over each day              - keeps one day's worth of logs, and does not compress it, to allow filebeat to catch up              - passes through the system properties used in each log event's meta data (tags, source version)               It can be enabled via logback.xml like this:               <appender name="STRUCTURED_LOGGING" class="com.timgroup.logger.FilebeatAppender"/>          * Graham Allan: gallan: enable users to configure this layout to insert a newline between log messages.             This is to enable writing structured events to a file that can be consumed by Filebeat before being set to Logstash. Filebeat's "json_lines" codec depends on reading a file of json objects each separated by a newline.  * changes to com.timgroup:tim-slogger_2.11:    * autobumper: Autobumper: com.timgroup:tim-logger:0.5-20170406-143535 -> com.timgroup:tim-logger:1.5.1073        * changes to com.timgroup:tim-logger:          * Graham Allan: gallan: bump major version to trump version I accidentally published locally.             Ensure version number from a local "gradle upload" doesn't accidentally beat what's uploaded by CI.          * Graham Allan: gallan: create an appender suitable for consumption by filebeat.             With zero configuration it:              - separates json by newlines, as required by Filebeat              - rolls over each day              - keeps one day's worth of logs, and does not compress it, to allow filebeat to catch up              - passes through the system properties used in each log event's meta data (tags, source version)               It can be enabled via logback.xml like this:               <appender name="STRUCTURED_LOGGING" class="com.timgroup.logger.FilebeatAppender"/>          * Graham Allan: gallan: enable users to configure this layout to insert a newline between log messages.             This is to enable writing structured events to a file that can be consumed by Filebeat before being set to Logstash. Filebeat's "json_lines" codec depends on reading a file of json objects each separated by a newline.
Autobumper: com.timgroup:tim-slogger_2.12:0.1.1069 -> com.timgroup:tim-slogger_2.12:0.1.1070, com.timgroup:tim-slogger_2.11:0.1.1069 -> com.timgroup:tim-slogger_2.11:0.1.1070
 * changes to com.timgroup:tim-slogger_2.12:
   * autobumper: Autobumper: com.timgroup:tim-logger:0.5-20170406-143535 -> com.timgroup:tim-logger:1.5.1073
       * changes to com.timgroup:tim-logger:
         * Graham Allan: gallan: bump major version to trump version I accidentally published locally.
            Ensure version number from a local "gradle upload" doesn't accidentally beat what's uploaded by CI.
         * Graham Allan: gallan: create an appender suitable for consumption by filebeat.
            With zero configuration it:
             - separates json by newlines, as required by Filebeat
             - rolls over each day
             - keeps one day's worth of logs, and does not compress it, to allow filebeat to catch up
             - passes through the system properties used in each log event's meta data (tags, source version)
              It can be enabled via logback.xml like this:
              <appender name="STRUCTURED_LOGGING" class="com.timgroup.logger.FilebeatAppender"/>
         * Graham Allan: gallan: enable users to configure this layout to insert a newline between log messages.
            This is to enable writing structured events to a file that can be consumed by Filebeat before being set to Logstash. Filebeat's "json_lines" codec depends on reading a file of json objects each separated by a newline.
 * changes to com.timgroup:tim-slogger_2.11:
   * autobumper: Autobumper: com.timgroup:tim-logger:0.5-20170406-143535 -> com.timgroup:tim-logger:1.5.1073
       * changes to com.timgroup:tim-logger:
         * Graham Allan: gallan: bump major version to trump version I accidentally published locally.
            Ensure version number from a local "gradle upload" doesn't accidentally beat what's uploaded by CI.
         * Graham Allan: gallan: create an appender suitable for consumption by filebeat.
            With zero configuration it:
             - separates json by newlines, as required by Filebeat
             - rolls over each day
             - keeps one day's worth of logs, and does not compress it, to allow filebeat to catch up
             - passes through the system properties used in each log event's meta data (tags, source version)
              It can be enabled via logback.xml like this:
              <appender name="STRUCTURED_LOGGING" class="com.timgroup.logger.FilebeatAppender"/>
         * Graham Allan: gallan: enable users to configure this layout to insert a newline between log messages.
            This is to enable writing structured events to a file that can be consumed by Filebeat before being set to Logstash. Filebeat's "json_lines" codec depends on reading a file of json objects each separated by a newline.
tim-group/tg-eventstore,tim-group/tg-eventstore