Update optimade requirement from ~=0.25.3 to ~=1.0.0

[dependabot[bot]]

Updates the requirements on optimade to permit the latest version.

Release notes

Sourced from optimade's releases.

v1.0.0

What's Changed

• Update requirements-client.txt by @​JPBergsma in Materials-Consortia/optimade-python-tools#1813
• Modernize all Python 3.8 annotations by @​ml-evs in Materials-Consortia/optimade-python-tools#1815
• Migration to pydantic v2 by @​ml-evs in Materials-Consortia/optimade-python-tools#1745
• Update dependencies by @​bot-optimade in Materials-Consortia/optimade-python-tools#1834
• Fix an inappropriate test expression to remove a logical short circuit by @​munahaf in Materials-Consortia/optimade-python-tools#1838
• Update dependencies by @​bot-optimade in Materials-Consortia/optimade-python-tools#1846
• Make client provider scraper more robust and add --version by @​ml-evs in Materials-Consortia/optimade-python-tools#1848
• Add test that checks whether client can find at least one base URL by @​ml-evs in Materials-Consortia/optimade-python-tools#1849
• Fix incorrect 'smart' union discrimination by @​ml-evs in Materials-Consortia/optimade-python-tools#1844
• Update dependencies by @​bot-optimade in Materials-Consortia/optimade-python-tools#1857
• Add Python 3.12 to CI by @​ml-evs in Materials-Consortia/optimade-python-tools#1858
• CI performance refresh by @​ml-evs in Materials-Consortia/optimade-python-tools#1836
• Try Python 3.9 in fly build to reduce memory usage by @​ml-evs in Materials-Consortia/optimade-python-tools#1860
• Disable inserting test data in fly demo server by @​ml-evs in Materials-Consortia/optimade-python-tools#1861
• Revert test data insertion and instead increase fly swap by @​ml-evs in Materials-Consortia/optimade-python-tools#1862
• Explicitly set builder for Fly by @​ml-evs in Materials-Consortia/optimade-python-tools#1863
• Debugging fly configuration by @​ml-evs in Materials-Consortia/optimade-python-tools#1864
• Manually generate Fly environment in CI by @​ml-evs in Materials-Consortia/optimade-python-tools#1865
• Try to resolve new fly builder deps by @​ml-evs in Materials-Consortia/optimade-python-tools#1866
• Update config file location for Fly deployment by @​ml-evs in Materials-Consortia/optimade-python-tools#1867
• Try to force fly to use the config file by @​ml-evs in Materials-Consortia/optimade-python-tools#1870
• Try to force fly to use the config file in Procfile by @​ml-evs in Materials-Consortia/optimade-python-tools#1871

New Contributors

• @​munahaf made their first contribution in Materials-Consortia/optimade-python-tools#1838

Full Changelog: https://github.com/Materials-Consortia/optimade-python-tools/compare/v0.25.3...v1.0.0

Changelog

v1.0.0 (2023-11-09)

Full Changelog

optimade-python-tools has reached v1.0.0!

We have decided to make this first major release at this point due to the arduous migration to pydantic v2 between v1.0.0 and v0.25.3. This will allow for improved compatibility with the rest of the ecosystem, plus all of the performance and ergonomics benefits of the new pydantic.

If you are using optimade-python-tools primarily as a library, then you may need to make some code changes to support the new version. For example, the underlying API for dealing with the pydantic models has changed (e.g., model.dict() is now model.model_dump()) -- a full migration guide can be found in the pydantic docs. Additionally, any cases where the underlying JSON schemas were being modified may need to be updated; internally we are pretty much exclusively operating on the pydantic model objects without needing to modify the raw schemas anymore.

Going forward, v1.0.x will be the last series to support v1.1 of the OPTIMADE specification, with future versions of the package v1.x.y adding features from the pre-release of OPTIMADE v1.2.

A branch will be maintained for the v0.25.x series will be maintained for those who are stuck on pydantic v1 and run into bugs. Please make it clear in any bug reports if you are using this version.

Fixed bugs:

• Deserialization regressions: cannot resolve child databases in client #1843
• Performance regressions following pydantic update #1835

... (truncated)

Changelog

Sourced from optimade's changelog.

v1.0.0 (2023-11-07)

Full Changelog

Fixed bugs:

• Deserialization regressions: cannot resolve child databases in client #1843
• Performance regressions following pydantic update #1835

Closed issues:

• Python 3.12 support #1859
• Remove nullable from schemas (for OpenAPI 3.1) #1814

Merged pull requests:

• Add Python 3.12 to CI #1858 (ml-evs)
• Add test that checks whether client can find at least one base URL #1849 (ml-evs)
• Make client provider scraper more robust and add --version #1848 (ml-evs)
• Fix incorrect 'smart' union discrimination #1844 (ml-evs)
• CI performance refresh #1836 (ml-evs)
• Modernize all Python 3.8 annotations #1815 (ml-evs)
• Migration to pydantic v2 #1745 (ml-evs)

v0.25.3 (2023-09-29)

Full Changelog

Merged pull requests:

• Add mp-api and emmet pins to avoid premature pydantic v2 upgrade #1795 (ml-evs)
• Debugging links->next issues #1794 (ml-evs)
• Add option for custom landing pages #1788 (ml-evs)
• Add config option mongo_count_timeout to skip the global count per request #1757 (ml-evs)

v0.25.2 (2023-09-12)

Full Changelog

Merged pull requests:

• Fix typo in pyproject.toml #1763 (ml-evs)

v0.25.1 (2023-08-10)

Full Changelog

This release simply tests the migration to pyproject.toml, as well as updating a few dependencies along the way.

Merged pull requests:

... (truncated)

Commits

• eaa4315 Release v1.0.0 - Changelog
• 6b6bda7 Try to force fly to use the config file in Procfile (#1871)
• 061093b Try to force fly to use the config file (#1870)
• 56f006e Update config file location for Fly deployment (#1867)
• ade6a42 Try to resolve new fly builder deps (#1866)
• 2da87b3 Manually generate Fly environment (#1865)
• 3bc7025 Debugging fly configuration (#1864)
• e25fd6e Explicitly set builder for Fly (#1863)
• bbb64d6 Revert test data insertion and instead increase fly swap (#1862)
• 71267ff Disable adding test data in demo server (#1861)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot[bot]]

Superseded by #573.