v0.6.3

= 0.6.3 =

• Security: Google API key no longer sent to the browser when using the Google geocoding provider.
• Fix: Google forward geocoding now returns results correctly (broken since v0.6.0 array response change).
• Fix: Classic editor strings are now translatable via __().
• Fix: ESLint configuration migrated to flat config required by @wordpress/scripts 32.x.
• Fix: Classic editor metabox saves lat/lng as float, matching the REST API save path.
• Add: Geo meta changes made by external callers (e.g. REST API writes) now sync the location taxonomy automatically.

v0.6.2

= 0.6.2 =

• Fix: Location Name block now loads correctly on live sites — block.json path updated to the compiled build directory.

v0.6.1

= 0.6.1 =

• Fix: Forward geocode now uses the Places API (New) with an optional user-supplied location bias, preventing server IP from skewing results on hosted environments.

v0.6.0

= 0.6.0 =

• Change: Geocode proxy now returns up to 5 candidate results instead of a single result.

v0.5.0

= 0.5.0 =

• Add: Location Name block (geotagr/location-name) — displays the place name attached to a post; renders nothing when no location is set.

v0.4.0

= 0.4.0 =

• Add: Nominatim, Google Places, and Mapbox geocoding providers — configurable from Settings.
• Add: Per-provider API key instructions with visibility toggle in the Settings page.
• Add: Server-side REST proxy for Google Places, keeping the API key out of the browser.
• Fix: Mapbox POI subtype handling (poi.landmark and similar) now correctly populates the place name.
• Fix: Whitespace normalisation applied before sending any geocoding query.