v0.7.0 release

[ml-evs]

This PR prepares another minor release that includes the changes from this week.

Breaking changes:

• optimade.server.mappers.ResourceMapper has been renamed as optimade.server.mappers.BaseResourceMapper (Validate all non-optional :filter: examples from the spec #213).

New features:

• Validation of all mandatory filter examples present in the specification (Validate all non-optional :filter: examples from the spec #213, @ml-evs.)
• New invoke task to scrape the filter examples from the specification (and new submodule optimade.validator.data for loading them (Validate all non-optional :filter: examples from the spec #213, @ml-evs, with bug fixes from @CasperWA in Add txt-files in optimade.validator.data to MANIFEST #225).
• Dependabot is now used to ensure requirements are updated in a timely manner and new versions of django (v3) and elasticsearch-dsl (v7) are now supported (@CasperWA, Update elasticsearch-dsl requirement from ~=6.4 to >=6.4,<8.0 #218, Update django requirement from >=2.2.9,~=2.2 to >=2.2,<4.0 #219).
• The GitHub action for the validator has been moved out of this repository, and over to Materials-Consortia/optimade-validator-action (Remove GH Action to validate OPTiMaDe instances #224, @CasperWA).

Bug fixes:

• Fixed handling of nested queries involving AND/OR and NOT for the mongo backend (Handle arbitrary nested NOT/AND/OR in queries #221, @ml-evs).

[codecov]

Codecov Report

Merging #228 into master will not change coverage by %.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #228   +/-   ##
=======================================
  Coverage   87.57%   87.57%           
=======================================
  Files          43       43           
  Lines        1916     1916           
=======================================
  Hits         1678     1678           
  Misses        238      238           

Flag	Coverage Δ
#unittests	87.57% <ø> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5569bda...acdbdf9. Read the comment docs.

[ml-evs]

Looks like I managed to tag the wrong commit for release (i.e. the one in this PR, not the resulting merge commit). Apologies! Assuming there are no other problems I will amend the commit message with the contents of the PR description, so just make sure that we rebase this PR.

This does seem like a problem, the PyPI release was created without anyone else reviewing the PR... I was under the impression it was only looking for commits to master?

[CasperWA]

Looks like I managed to tag the wrong commit for release (i.e. the one in this PR, not the resulting merge commit). Apologies! Assuming there are no other problems I will amend the commit message with the contents of the PR description, so just make sure that we rebase this PR.

Yup - first PR, then merge, then tag on master and git push --tags. But no worries. Maybe I should write a wiki page with the steps I usually follow?

This does seem like a problem, the PyPI release was created without anyone else reviewing the PR... I was under the impression it was only looking for commits to master?

No. It looks for tags in the repo.
We should probably be more stringent about it for sure.

[CasperWA]

Seems good though, cheers 👍 I'll merge it.