diff --git a/CHANGELOG.md b/CHANGELOG.md index 6958df03..6a8bc68e 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,6 +1,19 @@ ## Xarray-Spatial Changelog ----------- +### Version 0.4.0 - 2024-04-25 +- Python 3.12 is now supported! +- Python 3.9 & 3.8 are no longer supported. +- Documentation has also been moved to https://xarray-spatial.readthedocs.io/ + +Pull Requests merged in this release include: +- Add links to docs to readme (#800) +- Update readthedocs configuration (#798) +- Fix typo in readthedocs config (#799) +- Move docs to readthedocs (#797) +- Bunch of CI/CD-related fixes (#796) +- chore: Remove numpy pin, pin datashader, drop Python 3.7 (#789) + ### Version 0.3.7 - 2023-06-05 The 0.3.7 release is a hot fix for 0.3.6, which has problem with publishing to PyPi as the package exceeds the limit of 100MB. In this new release, example notebooks are diff --git a/RELEASE.md b/RELEASE.md index b08038d0..f95c1fdb 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -3,8 +3,6 @@ ### Preparation - Create a new branch containing the following changes: - Update CHANGELOG.md with new version number and list of changes extracted from `git log --pretty=oneline --pretty=format:"- %s" ..HEAD`. - - Add the new version reference in `xarray-spatial/docs/source/releases.json` - - Check that the new version number is included in `smv_tag_whitelist` in `docs/source/conf.py` so that the docs will be built and uploaded by CI. - Commit changes and submit them as a PR to the `master` branch. - If the CI passes OK, merge the PR. @@ -29,7 +27,8 @@ git push --tags - Click `Publish release`. ### Documentation -- When the github release is created, a github action automatically builds the documentation and uploads it to https://xarray-spatial.org/. This can take more than an hour to finish. + +- When the github release is created, a github action automatically builds the documentation and uploads it to https://xarray-spatial.readthedocs.io/. ### conda-forge packages - A bot in https://github.com/conda-forge/xarray-spatial-feedstock runs periodically to identify the new PyPI release and update the conda recipe appropriately. This should create a new PR, run tests to check that the conda build works, and automatically upload the packages to conda-forge if everything is OK. Check this works, a few hours after the PyPI release.