2023.2.22 release

.github/workflows/test.yml

@@ -129,7 +129,7 @@ jobs:
     if: github.event_name == 'release' || (github.event_name == 'workflow_dispatch' && inputs.task == 'release')
     strategy:
       matrix:
-        os: [macos-latest, windows-latest]
+        os: [macos-latest, windows-latest, ubuntu-latest]
         python-version: ['3.8', '3.9', '3.10']
     runs-on: ${{ matrix.os }}
 

ADMIN.md

@@ -5,11 +5,11 @@ following assumes you are using `miniconda` or Anaconda.
 
 ## Releases
 
-The general procedure to releasing `pymatgen` comprises the following
+The general procedure for releasing `pymatgen` comprises the following
 steps:
 
 1. Make sure all CI checks are green. We don't want to release known bugs.
-2. Update and edit change log.
+2. Update and edit changelog.
 3. Release PyPI versions + doc.
 4. Release `conda` versions.
 5. Release Dash documentation.

CHANGES.rst

@@ -1,6 +1,13 @@
 Change log
 ==========
 
+v2023.2.22
+----------
+* PR #2848 from @ml-evs ml-evs/update_optimade_aliases
+    Currently `OptimadeRester` defaults to an outdated list of OPTIMADE database URLs (several of which fail) and the design of the class is such that refreshing these aliases can only be done post-init which means they will not be used if the user provides their own filtered list of aliases, without doing some extra work.
+    This PR refreshes the vendored list of aliases (which should be much more stable now since their initial addition 2 years ago), and also adds the option to refresh the aliases on initialization of the class.
+    This currently affects the pymatgen OPTIMADE tutorials at https://github.com/Materials-Consortia/optimade-tutorial-exercises.
+
 v2023.1.30
 ----------
 * PR #2806 from @samblau qchem