Skip to main content
All notable changes to this project are documented in this file. The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
Version 0 of Semantic Versioning is handled differently from version 1 and above. The minor version will be incremented upon a breaking change and the patch version will be incremented for features.

[0.7.7] - 2026-02-25

Added

  • Adds two new possible planning designation enum values: buildingPreservationNotice and certificateOfImmunity (#392)
  • Adds two new site boundary additions: localPlanningAuthority and developmentCorporations (#392)
  • Adds metadata about any AI-enhanced components used in the service when applicable (#392)
  • Adds more granular fee breakdowns and Gov Pay metadata when applicable (#392, #394)
  • Adds user-defined drawing number when applicable to an uploaded file (#392)

[0.7.6] - 2025-10-23

Added

  • Adds optional properties id and tags to question metadata across all schemas which include responses (#383)
  • Adds file type biodivertyNetGainInformation to capture BNG requirements (#383)

Changed

  • data.report.boundary in the Enforcement schema is optional, rather than required, as not all users will provide this digitally (#383)
  • siteContact is optional, rather than required, for PreApplication as not all councils are consistently asking for this (#383)
  • Application type confirmationCompliance has simplified data.applicant requirements (#383)

[0.7.5] - 2025-05-29

Added

  • Adds “wards” to structured property data across all schemas, sourced from Planning Data (#353)
  • Adds a work-in-progress Enforcement schema, including example payloads (#354)

[0.7.4] - 2025-04-28

Added

  • Addition of “Historic battlefields” to PlanningDesignations enum (#334)

Changed

  • ProjectTypes enum values tidied up to remove duplicates and better align to GDPO classes (#332, #335)
  • Materials properties now account for Listed Building Consent variances (#331)

[0.7.3] - 2025-02-27

Added

  • CommunityInfrastructureLevy now includes all details collected by Form 1: Additional information (#312)
  • PlanningDesignations enum includes more datasets which may be incorporated into services soon based on Planning Data’s backlog (#311)

Changed

  • Minor type changes to Ownership definitions to better align to PlanX service content (#313)
  • Renames treePlan document to treeSurvey (#309)
  • Adjusts linked pre-application reference requirements (#298)

[0.7.2] - 2025-01-16

Changed

  • Updates CommunityInfrastructureLevy type to include “Not liable” path (#282)
  • Updates Flags enum values (#285)
  • Updates PlanningDesignation enum values (#286)
  • Updates PropertyTypes enum values (#287)

Added

  • Adds a work-in-progress PreApplication schema, including example payloads (#275)

[0.7.1] - 2024-11-07

Added

  • Explicit support for address ranges (#248)
  • Additional application types synced to PlanX service development - notably ldc.listedBuildingWorks and approval.conditions (#197)

[0.7.0] - 2024-07-12

Breaking

  • Updated ApplicationTypes, ProjectTypes and FileTypes based on ODP Service development across whole planning application ecosystem (#201, #200, #198, #197, #182, #177, #176)

Added

  • Added new example payloads and their associated types, now organised in subdirectories by application type (#183):
    • Minor planning permission (#193)
    • Major planning permission (#194)
    • Prior approvals (5 types) (#195, #186)
    • Land Drainage Consent (#187)
  • Added type definitions for Greater London Authority reporting requirements, like residential units etc (#192, #179, #178)
  • Added type definitions for “documents submitted as data” (not yet represented in example payloads) (#180)

Changed

  • Tightened type defintion for planning desigation “entities” (#196)
  • Upgraded a number of technical dependencies via Dependabot

Earlier Versions

For the complete changelog including versions 0.6.0 and earlier, please visit the GitHub repository.

Build docs developers (and LLMs) love