Release v0.3.1

[Theodore-Chatziioannou]

New release with the #263 bug fix

[codecov-commenter]

Codecov Report

Merging #265 (df0e6e7) into main (07813c8) will increase coverage by 0.69%.
Report is 157 commits behind head on main.
The diff coverage is 86.67%.

@@            Coverage Diff             @@
##             main     #265      +/-   ##
==========================================
+ Coverage   86.84%   87.54%   +0.69%     
==========================================
  Files          49       48       -1     
  Lines        5496     5747     +251     
  Branches     1372     1436      +64     
==========================================
+ Hits         4773     5031     +258     
+ Misses        462      447      -15     
- Partials      261      269       +8     

Files	Coverage Δ
pam/__init__.py	100.00% <100.00%> (ø)
pam/cli.py	85.80% <100.00%> (ø)
pam/planner/od.py	97.33% <ø> (-0.04%)	⬇️
pam/read/__init__.py	100.00% <ø> (ø)
pam/report/benchmarks.py	58.49% <100.00%> (ø)
pam/report/summary.py	93.12% <100.00%> (ø)
pam/samplers/tour.py	96.81% <100.00%> (+1.05%)	⬆️
pam/scoring.py	89.94% <100.00%> (+0.30%)	⬆️
pam/variables.py	100.00% <100.00%> (ø)
pam/write/__init__.py	100.00% <ø> (ø)
... and 12 more

... and 1 file with indirect coverage changes

📣 Codecov offers a browser extension for seamless coverage viewing on GitHub. Try it in Chrome or Firefox today!

[brynpickering]

@Theodore-Chatziioannou I see the v0.3.1 tag has already been used before the release of the stable package (i.e., this PR).

You'll need to move that tag to the commit in this branch to trigger the conda build. You can force update the tag while this branch is checked out: git tag -fa v0.3.1 -m "v0.3.1" and then git push -f --tag