From 3fa4f8db341af535598feebec65b55472bfbcb93 Mon Sep 17 00:00:00 2001 From: Jessica McInchak Date: Mon, 16 Oct 2023 22:06:07 +0200 Subject: [PATCH] v0.1.2 --- CHANGELOG.md | 27 ++++++++++++++++++++++++++- package.json | 2 +- 2 files changed, 27 insertions(+), 2 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 78ea8909..3a242a6e 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1 +1,26 @@ -// TODO once versioning is handled \ No newline at end of file +# Changelog + +All notable changes to this project are documented in this file. + +The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), +and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). + +**Note:** 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.1.1] - 2023-10-17 + +### Changed +- Adjusted shape of `data.property.constraints.planning` and added a `PlanningConstraint` definition ([#50](https://github.com/theopensystemslab/digital-planning-data-schemas/pull/50)) +- Added more granular values to the `ProjectType` definition ([#55](https://github.com/theopensystemslab/digital-planning-data-schemas/pull/55/files)) +- Improved examples, especially `data.proposal.details` ([#54](https://github.com/theopensystemslab/digital-planning-data-schemas/pull/54)) +- Minor naming and organisational adjustments throughout based on early feedback + +### Fixed +- Corrected usage of JSON Schema `Date` format ([#52](https://github.com/theopensystemslab/digital-planning-data-schemas/pull/52)) + +## [0.1.0] - 2023-10-04 + +### Added +- Released our first full working draft :tada: diff --git a/package.json b/package.json index 9f8dfe52..1261536b 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "digital-planning-data-schemas", - "version": "0.1.0", + "version": "0.1.1", "description": "Digital Planning Data schemas", "main": "schema/schema.json", "scripts": {