From fa518b806eaf64cb25d90cb3bf21bfb3dbd001ac Mon Sep 17 00:00:00 2001
From: Ben Newman <ben@meteor.com>
Date: Fri, 15 Nov 2019 10:47:11 -0500
Subject: [PATCH] Add some advice about republishing packages to History.md.

---
 History.md | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/History.md b/History.md
index b46397786b..25e1039bd9 100644
--- a/History.md
+++ b/History.md
@@ -25,6 +25,24 @@
   meteor npm install meteor-node-stubs@next
   ```
 
+* If you are the author of any Meteor packages, and you encounter errors
+  when using those packages in a Meteor 1.8.2 application (for example,
+  `module.watch` being undefined), we recommend that you bump the minor
+  version of your package and republish it using Meteor 1.8.2, so
+  Meteor 1.8.2 applications will automatically use the new version of the
+  package, as compiled by Meteor 1.8.2:
+  ```sh
+  cd path/to/your/package
+  # Add api.versionsFrom("1.8.2") to Package.onUse in package.js...
+  meteor --release 1.8.2 publish
+  ```
+  This may not be necessary for all packages, especially those that have
+  been recently republished using Meteor 1.8.1, or local packages in the
+  `packages/` directory (which are always recompiled from source).
+  However, republishing packages is a general solution to a wide variety
+  of package versioning and compilation problems, and package authors can
+  make their users' lives easier by handling these issues proactively.
+
 ### Changes
 
 * Node has been updated to version