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:
buildingPreservationNoticeandcertificateOfImmunity(#392) - Adds two new site boundary additions:
localPlanningAuthorityanddevelopmentCorporations(#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
idandtagsto question metadata across all schemas which includeresponses(#383) - Adds file type
biodivertyNetGainInformationto capture BNG requirements (#383)
Changed
data.report.boundaryin theEnforcementschema is optional, rather than required, as not all users will provide this digitally (#383)siteContactis optional, rather than required, forPreApplicationas not all councils are consistently asking for this (#383)ApplicationtypeconfirmationCompliancehas simplifieddata.applicantrequirements (#383)
[0.7.5] - 2025-05-29
Added
- Adds “wards” to structured
propertydata across all schemas, sourced from Planning Data (#353) - Adds a work-in-progress
Enforcementschema, including example payloads (#354)
[0.7.4] - 2025-04-28
Added
- Addition of “Historic battlefields” to
PlanningDesignationsenum (#334)
Changed
ProjectTypesenum values tidied up to remove duplicates and better align to GDPO classes (#332, #335)Materialsproperties now account for Listed Building Consent variances (#331)
[0.7.3] - 2025-02-27
Added
CommunityInfrastructureLevynow includes all details collected by Form 1: Additional information (#312)PlanningDesignationsenum includes more datasets which may be incorporated into services soon based on Planning Data’s backlog (#311)
Changed
- Minor type changes to
Ownershipdefinitions to better align to PlanX service content (#313) - Renames
treePlandocument totreeSurvey(#309) - Adjusts linked pre-application reference requirements (#298)
[0.7.2] - 2025-01-16
Changed
- Updates
CommunityInfrastructureLevytype to include “Not liable” path (#282) - Updates
Flagsenum values (#285) - Updates
PlanningDesignationenum values (#286) - Updates
PropertyTypesenum values (#287)
Added
- Adds a work-in-progress
PreApplicationschema, 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.listedBuildingWorksandapproval.conditions(#197)
[0.7.0] - 2024-07-12
Breaking
- Updated
ApplicationTypes,ProjectTypesandFileTypesbased 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):
- 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