Merge pull request #235 from stac-utils/release/v0.4.0

prepare for 0.4.0 release

Author: Phil Varner

CHANGELOG.md

@@ -6,6 +6,10 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
 
 ## [Unreleased] - TBD
 
+None
+
+## [v0.4.0] - 2022-06-08
+
 ### Added
 
 - Significantly improved type hints
@@ -201,7 +205,8 @@ are in a single HTTP session, handle pagination and respects conformance
 
 Initial release.
 
-[Unreleased]: <https://github.com/stac-utils/pystac-client/compare/v0.3.5...main>
+[Unreleased]: <https://github.com/stac-utils/pystac-client/compare/v0.4.0...main>
+[v0.4.0]: <https://github.com/stac-utils/pystac-client/compare/v0.3.5...v0.4.0>
 [v0.3.5]: <https://github.com/stac-utils/pystac-client/compare/v0.3.4..v0.3.5>
 [v0.3.4]: <https://github.com/stac-utils/pystac-client/compare/v0.3.3..v0.3.4>
 [v0.3.3]: <https://github.com/stac-utils/pystac-client/compare/v0.3.2..v0.3.3>

RELEASING.md

@@ -7,9 +7,8 @@
 4. Update [CHANGELOG.md](CHANGELOG.md).
    1. Add a new header under "Unreleased" with the new version and the date, e.g. `## [vX.Y.Z] - YYYY-MM-DD`.
    2. Audit the changelog section to ensure all changes are captured.
-   3. Add a new link reference at the bottom of the changelog with the new version.
+   3. Add a link reference for the new version after the Unreleased link reference at the bottom of the file.
       Follow the format from the previous version links.
-   4. Update the "Unreleased" link to reference your new version.
 5. (optional) Build the package locally and inspect its contents: `pip install build && python -m build`
 6. Open a pull request for your `release/vX.Y.Z` branch against the appropriate branch (either `main` or a version branch, e.g. `v0.3`).
    Include a section in the pull request description with the CHANGELOG contents for this version.

pystac_client/version.py

@@ -1 +1 @@
-__version__ = "0.3.5"
+__version__ = "0.4.0"