diff --git a/History.md b/History.md
index 922466535c..c618d2b0f3 100644
--- a/History.md
+++ b/History.md
@@ -1,5 +1,14 @@
 ## v.NEXT
 
+## v1.7.0.1, 2018-05-29
+
+* Reverted an [optimization](https://github.com/meteor/meteor/pull/9825)
+  introduced in Meteor 1.7 to stop scanning `node_modules` for files that
+  might be of interest to compiler plugins, since the intended workarounds
+  (creating symlinks) did not satisfy all existing use cases. We will
+  revisit this optimization in Meteor 1.7.1.
+  [mozfet/meteor-autoform-materialize#43](https://github.com/mozfet/meteor-autoform-materialize/issues/43)
+
 ## v1.7, 2018-05-28
 
 * More than 80% of internet users worldwide have access to a web browser
@@ -141,12 +150,13 @@
   application code. [PR #9771](https://github.com/meteor/meteor/pull/9771)
   [Feature #6](https://github.com/meteor/meteor-feature-requests/issues/6)
 
-  > Note: since compilation of npm packages can now be enabled using the
+  > ~Note: since compilation of npm packages can now be enabled using the
     techniques described above, Meteor will no longer automatically scan
     `node_modules` directories for modules that can be compiled by
     compiler plugins. If you have been using that functionality to import
     compiled-to-JS modules from `node_modules`, you should start using the
-    symlinking strategy instead.
+    symlinking strategy instead.~ **Follow-up note: this optimization was
+    reverted in Meteor 1.7.0.1 (see [above](#v1701-2018-05-29)).**
 
 * Node has been updated to version
   [8.11.2](https://nodejs.org/en/blog/release/v8.11.2/), officially fixing