Bump aiida-core from 2.4.2 to 2.5.0

[dependabot]

Bumps aiida-core from 2.4.2 to 2.5.0.

Release notes

Sourced from aiida-core's releases.

AiiDA v2.5.0

See CHANGELOG.md

Changelog

Sourced from aiida-core's changelog.

v2.5.0 - 2023-12-20

This minor release comes with a number of features that are focused on user friendliness of the CLI and the API. It also reduces the import time of modules, which makes the CLI faster to load and so tab-completion should be snappier. The release adds support for Python 3.12 and a great number of bugs are fixed.

• Create profiles without a database server
• Changes in process launch functions
• Improvements for built-in data types
• Repository interface improvements
• Full list of changes
  • Features
  • Performance
  • Changes
  • Fixes
  • Deprecations
  • Documentation
  • Dependencies
  • Devops

Create profiles without a database server

A new storage backend plugin has been added that uses SQLite instead of PostgreSQL. This makes it a lot easier to setup across all platforms. A new profile using this storage backend can be created in a single command:

verdi profile setup core.sqlite_dos -n --profile <PROFILE_NAME> --email <EMAIL>

Although easier to setup compared to the default storage backend that uses PostgreSQL, it is less performant. This makes this storage ideally suited for use-cases that want to test or demonstrate AiiDA, or to just play around a bit. The storage is compatible with most of AiiDA's functionality, except for automated database migrations and some very specific QueryBuilder functionality. Therefore, for production databases, the default core.psql_dos storage entry point remains the recommended storage.

It is now also possible to create a profile using an export archive:

verdi profile setup core.sqlite_dos -n --profile <PROFILE_NAME> --filepath <ARCHIVE>

where <ARCHIVE> should point to an export archive on disk. You can now use this profile like any other profile to inspect the data of the export archive. Note that this profile is read-only, so you will not be able to use it to mutate existing data or add new data to the profile. See the documentation for more details and a more in-depth example.

Finally, the original storage plugin core.psql_dos, which uses PostgreSQL for the database is also accessible through verdi profile setup core.psql_dos. Essentially this is the same as the verdi setup command, which is kept for now for backwards compatibility.

See the documentation on storage plugins for more details on the differences between these storage plugins and when to use which.

The verdi profile delete command can now also be used to delete a profile for any of these storage plugins. You will be prompted whether you also want to delete all the data, or you can specify this with the --delete-data or --keep-data flags.

... (truncated)

Commits

• d1c3922 Release v2.5.0
• 397a714 DynamicEntryPointCommandGroup: Temporarily silence deprecation warning (#6232)
• b168f2e Docker: Bump Python version to 3.10.13 (#6229)
• 9941266 Docs: Remove aiida.manage.configuration.load_documentation_profile (#6231)
• 0a9c278 Docs: Fix instructions for inspecting archive files (#6226)
• 6d18ccb Engine: Make process inputs in launchers positional (#6202)
• bfdb282 Devops: Bump upload-artifact action to v4 for Docker workflow (#6228)
• 5015f5f verdi profile delete: Make it storage plugin agnostic (#6224)
• a44363c Engine: Fix log report when submit=wait (#6225)
• ec2c6a8 ORM: Fix problem with detached DbAuthInfo instances (#6208)
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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 <dependency name> 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)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (b5f1277) 90.81% compared to head (ad2de6f) 90.81%.
Report is 18 commits behind head on dependabot_updates.

Additional details and impacted files

@@                 Coverage Diff                 @@
##           dependabot_updates    #1913   +/-   ##
===================================================
  Coverage               90.81%   90.81%           
===================================================
  Files                      75       75           
  Lines                    4661     4661           
===================================================
  Hits                     4233     4233           
  Misses                    428      428           

Flag	Coverage Δ
project	90.81% <100.00%> (ø)
validator	90.68% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.