Release 1.0.16

[caglarpir]

First release since 1.0.15 (2025-07-21). Bumps VERSION so the publish workflow can upload — it has been red on every push to main with:

400 File already exists ('mapillary-1.0.15-py3-none-any.whl')

PyPI never permits reusing a version number, so the job cannot go green until the version moves.

⚠️ Merging this publishes to PyPI immediately and irreversibly. pypi-publish.yml fires on push to main and uploads via OIDC trusted publishing. 1.0.16 can never be re-uploaded once it exists.

User-visible changes since 1.0.15

• fields=["id"] is now accepted on every entity type. It previously raised InvalidFieldError, even though the Graph API returns id and every decoded feature carries one. (Correct declared Python support and accept the 'id' field #184)
• save_locally() no longer writes inside the installed package. Its default was evaluated at import and resolved to the site-packages directory; it now resolves to the current working directory at call time, which is what the docstring always described. (Stop save_locally defaulting to the installed package directory #185)
• python_requires corrected from ">=3.0" to ">=3.10". The old value was not satisfiable — shapely>=2.1.0 requires >=3.10, so the package could never install below that. Classifiers updated to match, 3.13 and 3.14 added. Anyone on an older interpreter keeps resolving to 1.0.15 rather than getting a broken install. (Correct declared Python support and accept the 'id' field #184)
• A dead reference link in the exif_orientation docstrings now points at an archived copy instead of a host that no longer resolves. (Fix two broken documentation links #187)

Everything else merged since 1.0.15 — the lockfile refresh (#183), CI repairs (#179, #188) and the Docusaurus 3 upgrade (#186) — does not affect installed behaviour.

Version number

1.0.16 rather than 1.1.0, following the project's convention: every release from 1.0.4 through 1.0.15 has been a patch bump. Worth noting that the save_locally and python_requires changes are arguably minor-bump material under strict semver, so if you would rather signal them more loudly, say and I will change it before merge.

Verified before release

Built the artifacts and tested them rather than assuming:

Version          1.0.16
Requires-Python  >=3.10
classifiers      3.10 3.11 3.12 3.13 3.14

installed from the wheel into a clean 3.13 venv:
  id field         True
  save default     None  (resolves to cwd)
  live query       22524 features
  saved to cwd     [rel.geojson]

twine check mapillary-1.0.16-py3-none-any.whl   PASSED
twine check mapillary-1.0.16.tar.gz             PASSED

twine check is what PyPI validates on upload, so this should not fail at the last step.

Also fixed

pypi-publish.yml had environment.url: https://pypi.org/p/notehub-py — an unrelated project, copy-pasted from elsewhere. It is only the display link in the GitHub UI, not part of the OIDC exchange, so the publish was unaffected; but it pointed somewhere wrong. Now pypi.org/p/mapillary.

Post-merge

The repo tags releases (v1.0.12 and earlier) but the recent ones are untagged. Worth adding v1.0.16 and a GitHub release entry if you want to restore that.