Add M1 github actions

.github/workflows/build.yml

@@ -16,8 +16,11 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        os: ['ubuntu-latest', 'macos-latest', 'windows-latest']
+        os: ['ubuntu-latest', 'macos-latest', 'windows-latest', 'macos-14']
         python-version: ['3.9', '3.10', '3.11']
+        exclude:
+          - os: 'macos-14'
+            python-version: '3.9'
     env:
       MPLBACKEND: Agg  # https://github.com/orgs/community/discussions/26434
     steps:

CHANGELOG.md

@@ -13,7 +13,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/).
 ### Fixed
  - Fixed issue with calendar generation when the (rightmost) target period crossed into the new year ([#70](https://github.com/AI4S2S/lilio/pull/70)).
  - Fixed issue with Pandas 2.2 where 'M' changed to 'ME' ([#72](https://github.com/AI4S2S/lilio/pull/72))
-  - Fixed issue where pd.Interval now shows time where it is not wanted ([#72](https://github.com/AI4S2S/lilio/pull/72)). The issue was raised with Pandas ([#57748] https://github.com/pandas-dev/pandas/issues/57748).
+ - Fixed issue where pd.Interval now shows time where it is not wanted ([#72](https://github.com/AI4S2S/lilio/pull/72)). The issue was raised with Pandas ([#57748] https://github.com/pandas-dev/pandas/issues/57748).
+ - Added tests for latest version of macos (with M1 chips) ([#73](https://github.com/AI4S2S/lilio/pull/73))
 
 ## 0.4.2 (2024-01-19)
 ### Changed

docs/project_setup.md

@@ -11,9 +11,9 @@ checklist](https://guide.esciencecenter.nl/#/best_practices/checklist).
 
 This repository is set up with Python versions:
 
-- 3.8
 - 3.9
 - 3.10
+- 3.11
 
 Add or remove Python versions based on project requirements. See [the
 guide](https://guide.esciencecenter.nl/#/best_practices/language_guides/python) for more information about Python
@@ -52,7 +52,7 @@ help you decide which tool to use for packaging.
 
 - Documentation should be put in the `lilio/docs/` directory. The contents have been generated using `sphinx-quickstart` (Sphinx version 1.6.5).
 - We recommend writing the documentation using Restructured Text (reST) and Google style docstrings.
-  - [Restructured Text (reST) and Sphinx CheatSheet](https://thomas-cokelaer.info/tutorials/sphinx/rest_syntax.html)
+  - [Restructured Text (reST) and Sphinx CheatSheet](https://sphinx-tutorial.readthedocs.io/cheatsheet/)
   - [Google style docstring examples](http://sphinxcontrib-napoleon.readthedocs.io/en/latest/example_google.html).
 - The documentation is set up with the ReadTheDocs Sphinx theme.
   - Check out its [configuration options](https://sphinx-rtd-theme.readthedocs.io/en/latest/).