Major release 1.0.0 🎉

Signed-off-by: Anurag Tiwari <[email protected]>

CHANGELOG.MD

@@ -4,6 +4,17 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.0.0] - 2019-09-11
+
+### Added
+  - Support for PubSub.
+  - Setter/getter for pubsub client.
+  - `trigger_event!` to push messages to pubsub client.
+  - Unit tests for pubsub integration.
+
+### Changed
+  - `finish!` params. (Takes status, clear and data)
+
 ## [0.1.7] - 2019-07-19
 
 ### Added

Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    transaction (0.1.7)
+    transaction (1.0.0)
       redis (>= 4.0.2)
 
 GEM

lib/transaction/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Transaction
-  VERSION = '0.1.7'
+  VERSION = '1.0.0'
 end

transaction.gemspec

@@ -10,8 +10,15 @@ Gem::Specification.new do |spec|
   spec.authors       = ['Anurag Tiwari']
   spec.email         = ['[email protected]']
 
-  spec.summary       = 'Record status along with other relevant information of transactions/tasks.'
-  spec.description   = 'Record status along with other relevant information of transactions/tasks.'
+  spec.summary       = 'Manage any task | transaction efficiently'
+  spec.description   = 'Record status along with other relevant information of
+  transactions or tasks. These tasks can be a cron job, large background jobs or
+  a simple method. Any task can be plugged into a transaction block. Transaction
+  uses Redis to store the current status along with other information.
+  The events within the transaction block can be published via Pubsub client
+  (ex. Pusher, PubNub or any valid pubsub client).These events can be
+  subscribed in the client app for the live status of the transaction.'
+
   spec.homepage      = 'https://github.com/t2013anurag/transaction'
   spec.license       = 'MIT'