Adding getCurrentPackage docs back

Author: lostintangent

README.md

@@ -378,6 +378,8 @@ When you require `react-native-code-push`, the module object provides the follow
 
 * [checkForUpdate](#codepushcheckforupdate): Asks the CodePush service whether the configured app deployment has an update available. 
 
+* [getCurrentPackage](#codepushgetcurrentpackage): Retrieves the metadata about the currently installed update (e.g. description, installation time, size). *NOTE: As of `v1.10.3-beta` of the CodePush module, this method is deprecated in favor of [`getUpdateMetadata`](#codepushgetupdatemetadata)*.
+
 * [getUpdateMetadata](#codepushgetupdatemetadata): Retrieves the metadata for an installed update (e.g. description, mandatory).
 
 * [notifyApplicationReady](#codepushnotifyapplicationready): Notifies the CodePush runtime that an installed update is considered successful. If you are manually checking for and installing updates (i.e. not using the [sync](#codepushsync) method to handle it all for you), then this method **MUST** be called; otherwise CodePush will treat the update as failed and rollback to the previous version when the app next restarts.
@@ -417,6 +419,39 @@ codePush.checkForUpdate()
 });
 ```
 
+#### codePush.getCurrentPackage
+
+*NOTE: This method is considered deprecated as of `v1.10.3-beta` of the CodePush module. If you're running this version (or newer), we would recommend using the [`codePush.getUpdateMetadata`](#codepushgetupdatemetadata) instead, since it has more predictable behavior.*
+
+```javascript
+codePush.getCurrentPackage(): Promise<LocalPackage>;
+```
+
+Retrieves the metadata about the currently installed "package" (e.g. description, installation time). This can be useful for scenarios such as displaying a "what's new?" dialog after an update has been applied or checking whether there is a pending update that is waiting to be applied via a resume or restart.
+
+This method returns a `Promise` which resolves to one of two possible values:
+
+1. `null` if the app is currently running the JS bundle from the binary and not a CodePush update. This occurs in the following scenarios:
+
+    1. The end-user installed the app binary and has yet to install a CodePush update
+    1. The end-user installed an update of the binary (e.g. from the store), which cleared away the old CodePush updates, and gave precedence back to the JS binary in the binary.
+
+2. A [`LocalPackage`](#localpackage) instance which represents the metadata for the currently running CodePush update.
+
+Example Usage: 
+
+```javascript
+codePush.getCurrentPackage()
+.then((update) => {
+    // If the current app "session" represents the first time
+    // this update has run, and it had a description provided
+    // with it upon release, let's show it to the end user
+    if (update.isFirstRun && update.description) {
+        // Display a "what's new?" modal
+    }
+});
+```
+
 #### codePush.getUpdateMetadata
 
 ```javascript