Skip to content

Releases

v2.1.0 — fix reverse_lookup correctness bug, add max_km

Choose a tag to compare

@devzoy devzoy released this 19 Sep 16:35

Fixes a real correctness bug in `reverse_lookup`/`reverseLookup` reported by a user, plus a new optional parameter. Fully backward-compatible — safe to upgrade from any 2.x version.

Fixed

  • `reverse_lookup`/`reverseLookup` could return the wrong pincode (both Python and Node). The expanding nearest-neighbor search stopped at the first non-empty search box and returned the closest point within that box — but a genuinely closer point can sit just outside, near a corner. Verified against a brute-force haversine scan over all 19,416 centroids: Python was wrong on ~1.25–2% of queries near real centroids before the fix, 0/2000 after.
  • Monorepo root `package.json` version had drifted from `version.json`. Fixed, and it's now a managed 5th manifest so this can't recur.
  • README accuracy table incorrectly listed pincode `682555` as a cross-state example — it's actually single-state Lakshadweep. Replaced with `110025`, with a note that some "cross-state" pincodes are source-data mis-codings rather than genuine boundary cases.

Added

  • `reverse_lookup(lat, lon, max_km=None)` / `reverseLookup(lat, lon, maxKm)`: returns `None`/`null` instead of a misleadingly confident match once the nearest pincode exceeds that distance (e.g. for offshore coordinates).

Full details in CHANGELOG.md, including two documented known gaps for a future release.

🤖 Generated with Claude Code

v2.0.1 — comprehensive READMEs, repo cleanup

Choose a tag to compare

@devzoy devzoy released this 19 Sep 15:30

Docs-only release. No API or data changes — safe to upgrade from 2.0.0 with zero code changes.

What changed

  • Rewrote all 5 READMEs (root + @devzoy/indian-pincode, @devzoy/indian-pincode-geo, indian-pincode, indian-pincode-geo) with full API reference tables, an honest library-vs-API comparison, accuracy examples, data-quality details, and an FAQ. Every example output in these docs was verified against the real installed 2.0.0 packages before being written down.
  • Removed docs/AUDIT.md, an internal planning document from the v2 rebuild whose findings have all since been resolved.

Full details in CHANGELOG.md.

🤖 Generated with Claude Code

v1.0.4 - Fix API inconsistencies and add missing features

Choose a tag to compare

@devzoy devzoy released this 27 Nov 06:52

Fixed

  • Standardized distance field to distance (was distance_km) in both Python and Node.js
  • Added missing pincode field to Node.js findNearby() results
  • Added new searchByDistrict() function to Node.js library

Tested

  • ✅ All Python library functions
  • ✅ All Node.js library functions including new searchByDistrict()

Changes

  • Python: find_nearby() now returns distance instead of distance_km
  • Node.js: findNearby() now includes pincode field and uses distance instead of distance_km
  • Node.js: New searchByDistrict() function to search pincodes by district name

v1.0.3 - Documentation Updates

Choose a tag to compare

@devzoy devzoy released this 27 Nov 02:30

Documentation Improvements

  • ✅ Fixed installation commands in README
    • Python: Now correctly shows pip install indian-pincode
    • Node.js: Now correctly shows npm install @devzoy/indian-pincode
  • 📦 Added package size notice to help users make informed decisions
    • Clarified that this library is ~41MB (Node.js) and ~10MB (Python)
    • Explained target audience: applications prioritizing 100% uptime and offline capability
  • 🎯 Better set expectations about when to use this library vs. API-based solutions

v1.0.2

Choose a tag to compare

@devzoy devzoy released this 26 Nov 20:21

Release v1.0.2

  • Added comprehensive Node.js README with installation, usage examples, and API reference
  • Updated package versions to 1.0.2 for both Node.js and Python
  • Synchronized versions across all packages

v1.0.1

Choose a tag to compare

@devzoy devzoy released this 26 Nov 20:00

Release v1.0.1