Exclude spaCy 3.8.15 on Python 3.14

3.8.15 has the same defect as 3.8.14: neither a cp314 wheel nor an
sdist, so there is nothing installable on 3.14 (3.8.13 ships both).
CI resolved to it and failed at install.

Scoped to 3.14 with a marker so other interpreters still track the
latest spaCy, and left as exclusions so a release that restores cp314
artifacts is picked up without another change here.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: wrignj08

CHANGELOG.md

@@ -10,6 +10,7 @@
 - `vector_source` parameter on `make_water_mask` and `make_water_mask_debug`, accepting `"overture"` (default) or `"osm"`.
 - `include_ocean` parameter (default True). Overture's `ocean` water features cover everything seaward of the OSM coastline — signal the previous OSM tag set had no equivalent for, since it did not query `natural=coastline`. Set to False where coastline/tide offsets cause false positives.
 - `overturemaps>=1.0.0` dependency. `osmnx` is retained for the `vector_source="osm"` path.
+- The spaCy exclusion now covers 3.8.15 as well as 3.8.14, and is scoped to Python 3.14 with an environment marker. Both releases publish neither a cp314 wheel nor an sdist, so there is nothing installable on 3.14; 3.8.13 ships both. Other interpreters are no longer held back by the exclusion, and a later release that restores cp314 artifacts will be picked up without another change here.
 - The declared `pyarrow` floor is raised from 10.0.0 to 15.0.2. `overturemaps` requires that version, so 10.0.0 was never actually installable alongside it; the old floor only misdescribed what the package supports.
 
 ### Fixed

pyproject.toml

@@ -26,11 +26,14 @@ dependencies = [
     "tqdm>=4.0",
     "platformdirs>=4.0.0",
     "fastai>=2.7",
-    # spaCy 3.8.14 advertises Python 3.14 support but does not publish an
-    # installable cp314 artifact for the GitHub Actions Linux runner. This is a
-    # wheel availability problem, so it does not apply to distributions that
-    # build from source — the conda-forge recipe should not carry this exclusion.
-    "spacy!=3.8.14",
+    # spaCy 3.8.14 and 3.8.15 publish neither a cp314 wheel nor an sdist, so on
+    # Python 3.14 there is nothing for the resolver to install; 3.8.13 and
+    # earlier ship both. Scoped to 3.14 so other interpreters, where these
+    # versions install fine, are not held back, and expressed as exclusions so a
+    # later release that restores cp314 artifacts is picked up automatically.
+    # This is purely about what PyPI carries, so distributions that build from
+    # source — the conda-forge recipe — should not mirror it.
+    "spacy!=3.8.14,!=3.8.15; python_version >= '3.14'",
 ]
 license = "MIT"
 license-files = ["LICENSE"]