0.6.0 release

[vincentsarago]

initial we planned to do a 0.6 release with all the latest changes

geojson-pydantic/CHANGELOG.md

Lines 8 to 50 in 96eb472

	## [0.6.0] - TBD
	### Added
	- Enforce required keys and avoid defaults. This aim to follow the geojson specification to the letter.
	```python
	# Before
	Feature(geometry=Point(coordinates=(0,0)))
	# Now
	Feature(
	type="Feature",
	geometry=Point(
	type="Point",
	coordinates=(0,0)
	),
	properties=None,
	)
	```
	- Add has_z function to Geometries (author @eseglem, https://github.com/developmentseed/geojson-pydantic/pull/103)
	- Add optional bbox to geometries. (author @eseglem, https://github.com/developmentseed/geojson-pydantic/pull/108)
	- Add support for nested GeometryCollection and a corresponding warning. (author @eseglem, https://github.com/developmentseed/geojson-pydantic/pull/111)
	### Changed
	- Refactor and simplify WKT construction (author @eseglem, https://github.com/developmentseed/geojson-pydantic/pull/97)
	- Support empty geometry coordinates (author @eseglem, https://github.com/developmentseed/geojson-pydantic/pull/100)
	- Refactored `__geo_interface__` to be a Mixin which returns `self.dict` (author @eseglem, https://github.com/developmentseed/geojson-pydantic/pull/105)
	- GeometryCollection containing a single geometry or geometries of only one type will now produce a warning. (author @eseglem, https://github.com/developmentseed/geojson-pydantic/pull/111)
	### Fixed
	- Do not validates arbitrary dictionaries. Make `Type` a mandatory key for objects (author @vincentsarago, https://github.com/developmentseed/geojson-pydantic/pull/94)
	- Add Geometry discriminator when parsing geometry objects (author @eseglem, https://github.com/developmentseed/geojson-pydantic/pull/101)
	- Mixed Dimensionality WKTs (make sure the coordinates are either all 2D or 3D) (author @eseglem, https://github.com/developmentseed/geojson-pydantic/pull/107)
	- Allow Feature's **id** to be either a String or a Number (author @vincentsarago, https://github.com/developmentseed/geojson-pydantic/pull/91)
	### Removed
	- Python 3.7 support (author @vincentsarago, https://github.com/developmentseed/geojson-pydantic/pull/94)
	- Unused `LinearRing` Model (author @eseglem, https://github.com/developmentseed/geojson-pydantic/pull/106)

I think those changes are so important that we should do a 1.0 instead

any though? @eseglem @geospatial-jeff

[eseglem]

Might be worth putting everything out as a 0.6 and let users provide some feedback given the number of breaking changes. Maybe a 0.6 and then an rc1 at some set time in the future?

We could also consider waiting on a Pydantic v2 release to see if we can fix any of the remaining issues / PRs. I don't know how others are going to handle it, but I don't know if having a change like that on a minor release makes sense. Feels more like a major release to me.

I do have one more idea for BBox and being able to add a little more enforcement to it. And if it works out, would probably be good to get it in the same release. Whatever it is. So I'll try and throw that together soon.

[vincentsarago]

We could also consider waiting on a Pydantic v2 release

oh forget about this 🤦, yeah let's wait until then.

Just an update that we're aiming for an alpha release of Pydantic V2 by the end of March.

from pydantic/pydantic#4887 (comment)

or we could do 0.6 with what we have right now, and do a 1.0 when we switch to pydantic 2.0

in any case we should do an alpha release first 👍

[vincentsarago]

made a 0.6.0a0 release https://pypi.org/project/geojson-pydantic/0.6.0a0/

[vincentsarago]

FYI I just pushed 0.6 https://github.com/developmentseed/geojson-pydantic/releases/tag/0.6.0