diff --git a/.github/workflows/wheels.yml b/.github/workflows/wheels.yml
index 9dec7f23..13fa579f 100644
--- a/.github/workflows/wheels.yml
+++ b/.github/workflows/wheels.yml
@@ -199,7 +199,7 @@ jobs:
           token: ${{ secrets.GITHUB_TOKEN }}
 
       - name: Publish prep
-        if: ${{ (github.event_name == 'release') && (runner.os == 'Linux') }}
+        if: ${{ (github.event_name == 'release') }}
         run: |
           mywhl=`find ~/ -name "antspyx*.whl"`
           extrawheeldir=`dirname $mywhl`
diff --git a/README.md b/README.md
index 846a3efc..33eb07d4 100644
--- a/README.md
+++ b/README.md
@@ -28,9 +28,17 @@ pip install antspyx
 ```
 
 Because of limited storage space, pip binaries are not available for every combination of python
-version and platform. If we do not have releases for your platform on PyPI, you can check the
+version and platform. We also have had to delete older releases to make space. If you
+cannot find a binary you need on PyPI, you can check the
 [Releases](https://github.com/antsx/antspy/releases) page for archived binaries.
 
+Some Mac OS Python installations have compatibility issues with the pre-compiled
+binaries. This means pip will not install binaries targeted for the current Mac OS
+version, and will instead try to compile from source. The compatibility checks can be
+disabled by setting the  environment variable `SYSTEM_VERSION_COMPAT=0`. More details on
+the [wiki](https://github.com/ANTsX/ANTsPy/wiki/MacOS-wheel-compatibility-issues).
+
+
 ### Building from source
 
 In some scenarios, it can make sense to build from source. In general, you can build ANTsPy as you would any other Python package.