# Changelog of Building Permits Scraper — Construction Leads (US & Canada) (`opendatafrontierlab/us-building-permits`) Actor

- **URL**: https://apify.com/opendatafrontierlab/us-building-permits/changelog.md
- **Full Actor documentation**: https://apify.com/opendatafrontierlab/us-building-permits.md

## Changelog

### 1.0.7 (2026-10-29)

- **Charge-limit fix.** When a run reaches your maximum charge, a permit the budget can't cover is no longer marked as
  seen, so with `onlyNewSinceLastRun` you get it on the next run instead of losing it. Prices are unchanged.

### 1.0.6 (2026-10-29)

- **New York City (DOB NOW) record IDs changed. Please read this if you dedupe downstream.**
  - Before 1.0.6, `id` was `new-york-ny:<work_permit>`, so renewals and multiple work types of the same permit
    overwrote each other.
  - From 1.0.6, `id` is `new-york-ny:<work_permit>#<sequence_number>#<work_type>`. DOB NOW publishes one row per
    renewal sequence and work type, and each row is now its own record.
  - Effect: NYC runs return **more rows per permit**, and each row is billed as one `permit-record`.
  - If you key on `id`, NYC records from before and after 1.0.6 won't match. Use `permitNumber` (the base work
    permit number) to group them.
  - `onlyNewSinceLastRun`: permits you already received under the old ID format are still skipped, so you won't
    be re-billed for them. Their extra renewal or work-type rows are not delivered.
- Cincinnati (same release batch): `id` includes the permit type (`<permitnum>#<permit type>`), because the portal publishes one line per
  permit type.