docs(PUBLISHING): update with details about prebuilding binaries

PUBLISHING.md

@@ -10,8 +10,25 @@ Two factor auth is required for publishing.
 
 If publishing more than 3 packages at once and one of them is the bindings package, you'll need to figure out a way to get the ci's to build the binaries as github wont tell them about the new tags. You can do this by deleting the tag and pushing it again for the bindings package (only binary package as of this writing).
 
-For example for version 2.0.3
+CI will only prebuild binaries if the latest commit has tags that match the current branch and the `BINARY_BUILDER` environment variable is set to `true`.
+
+For example for version 2.0.3:
+
+Check the list of tags in the latest commit.
+
+```
+git tag --points-at HEAD
+```
+
+That should contain `@serialport/[email protected]`.
+
+If not, remove the remote tag and create the tag locally before updating the git remote.
+
 ```
 git push --delete origin @serialport/[email protected]
 git push origin @serialport/[email protected]
 ```
+
+Note:
+
+CI sets the `prebuild_upload` environment variable with a GitHub token to trigger `prebuild` to upload the binaries to the release tag. This is already configured on Travis and AppVeyor.