Skip to content

Releases: EMMC-ASBL/oteapi-core

v1.0.1

07 Dec 23:28

Choose a tag to compare

Changelog

v1.0.1 (2025-12-07)

Full Changelog

Update dependencies and dev tools

Auditing dependencies during CI/CD has been shifted from safety to pip-audit.
Dependencies have been updated, some with new minimum versions, others with a widened version range.
GH Actions and dev tools have been updated as well.

Fixed bugs:

  • pysftp is failing due to paramiko #617
  • There is currently an issue with pytest-celery #613

Merged pull requests:

* This Changelog was automatically generated by github_changelog_generator

v1.0.0

09 Apr 07:34

Choose a tag to compare

Changelog

v1.0.0 (2025-04-09)

Full Changelog

OTEAPI Core v1

This release marks the upgrade from in-development versions to a proper v1.
It represents the vast work that has gone into the OTE work through various EU projects; developing and utilizing the technology to bring semantically documented data through to simulators and other software that can specify what they desire, semantically, and subsequently retrieve it through OTE pipelines.

Drop Python 3.9 support

With this version Python 3.9 support is also dropped.
This will be propagated through the other relevant OTE repositories.

The minimum required Python version is now Python 3.10.
Python 3.13 test runs are added to the CI workflows.

Remove triple store module

The oteapi.triplestore module has been removed, along with all other triple store-related modules and files.
This move is done because this feature had not been properly integrated and other tools have been developed since that can utilize triple stores, for example tripper.
Furthermore, this aspect should be supported by the utilized interoperability software, for example DLite og vanilla SOFT.

Implemented enhancements:

  • Drop Python 3.9 support #592
  • Remove Session for the strategy interfaces #410

Merged pull requests:

* This Changelog was automatically generated by github_changelog_generator

v0.7.0

07 Apr 11:33

Choose a tag to compare

Changelog

v0.7.0 (2025-04-07)

Full Changelog

Use Pydantic v2 and a more minimized usage of session

Pydantic has been updated to use v2. This is a breaking change for existing plugins relying on pydantic v1, and the transition period has been longer than expected for letting plugin developers migrate.

A larger change is the change in the manner session is implemented. It is no longer provided as a parameter to strategy methods, but rather it is an object that lives only on the side of the OTE client, meaning it is something that comes on top of/outside of the realm of invoking a strategy. As is the concept of a pipeline, as it has always been.

See the full list of v0.7.0.devX changelog entries for a complete list of changes since v0.6.

Closed issues:

  • Remove maintenance (and support) for pydantic v1 #522

Merged pull requests:

  • Remove all things about keeping pydantic v1 support #591 (@CasperWA)

v0.7.0.dev6 (2024-11-25)

Full Changelog

Patch update - avoid Pydantic v2.10

This version of Pydantic currently breaks a lot of functionality around the Url models/classes.

Currently, we avoid v2.10.0 and v2.10.1.
This means the v2.10.2 (when released) should open a dependabot PR and it can be tested.

Note, it should be tested from OTEAPI Services, because this is where it failed most recently.

Fixed bugs:

* This Changelog was automatically generated by github_changelog_generator

v0.7.0.dev6

25 Nov 14:22

Choose a tag to compare

Changelog

v0.7.0.dev6 (2024-11-25)

Full Changelog

Patch update - avoid Pydantic v2.10

This version of Pydantic currently breaks a lot of functionality around the Url models/classes.

Currently, we avoid v2.10.0 and v2.10.1.
This means the v2.10.2 (when released) should open a dependabot PR and it can be tested.

Note, it should be tested from OTEAPI Services, because this is where it failed most recently.

Fixed bugs:

* This Changelog was automatically generated by github_changelog_generator

v0.7.0.dev5

25 Nov 12:46

Choose a tag to compare

Changelog

v0.7.0.dev5 (2024-11-25)

Full Changelog

Fix pydantic import issues

Minor patch release to fix imports from pydantic.networks for the latest Pydantic version (2.10).

Fixed bugs:

* This Changelog was automatically generated by github_changelog_generator

v0.7.0.dev4

20 Nov 08:14

Choose a tag to compare

Changelog

v0.7.0.dev4 (2024-11-20)

Full Changelog

Support Python 3.13

Add support for Python 3.13 in both the package metadata, but also through testing and minor code fixes.

Miscellaneous

Add MatCHMaker to the Acknowledgement section of the README.

Update Python dependencies and GitHub Actions.

Implemented enhancements:

  • Support Python 3.13 #538

Merged pull requests:

* This Changelog was automatically generated by github_changelog_generator

v0.7.0.dev3

09 Sep 13:31

Choose a tag to compare

Changelog

v0.7.0.dev3 (2024-09-09)

Full Changelog

Extend customization for http(s) download strategy

The http/https download strategy now supports several strategy-specific configurations for customizing the HTTP request.

DX updates

The CI/CD system has been overhauled, removing usage of the permanent dependencies branch and instead using dependabot's groups feature.
Furthermore, Trusted Publishers for PyPI has been implemented.

Implemented enhancements:

  • Support headers and more for download strategy #524

Fixed bugs:

  • pre-commit config should be updated to state master instead of main #469

Closed issues:

  • Use Trusted Publishers from PyPI #526

Merged pull requests:

* This Changelog was automatically generated by github_changelog_generator

v0.7.0.dev2

05 Jul 12:41

Choose a tag to compare

Support Python 3.12

Official support for Python 3.11 and 3.12 has been added, with the handling of the new entry points API. The old entry points API has been deprecated since Python 3.10 and support has been removed in Python 3.12.

Changelog

v0.7.0.dev2 (2024-07-05)

Full Changelog

Closed issues:

  • Update use of importlib.metadata.entry_points #395

Merged pull requests:

* This Changelog was automatically generated by github_changelog_generator

v0.7.0.dev1

08 Mar 13:27

Choose a tag to compare

Minimize configurations passed to stategies upon creation

When creating a strategy with a pydantic data model configuration it is always dumped/serialized to a Python dict. In order to ensure only the relevant user set configuration settings are passed on to the strategy, it must be dumped/serialized using the exclude_unset=True option.

Update resource/url strategy

This has been updated to return AttrDict instances and also a similarly "minimized" result from its get() method.

Changelog

v0.7.0.dev1 (2024-03-08)

Full Changelog

Merged pull requests:

* This Changelog was automatically generated by github_changelog_generator

v0.7.0.dev0

29 Feb 14:22

Choose a tag to compare

Major reworking of the OTE strategy design and philosophy

Simplified session handling

Sessions are now no longer passed in as a separate parameter to any strategy method. Instead it is handled by the OTEAPI Services and merged into the strategy-specific configuration (the configuration key's value) before initializing/creating a strategy.
The merging is done in a basic, conflict-free way at this point, meaning if a key/value-pair in the session would overwrite an existing key in the specific configuration, while the value differs, the merging is stopped and an exception is raised.

The actual merging logic is implemented in this repository and will/should be extended in the future to allow for different merging strategies to be defined and setup by end-users.

Updated Parser and Resource strategy purposes

Parser strategy

The Parser strategy's purpose is not to create and "execute" a Download strategy, parsing the downloaded object afterwards, according to its implementation.
This means the Download strategies will no longer be used directly, but rather only indirectly through the Parser strategies.

Resource strategy

The Resource strategy is no longer meant to represent a REST API service or similar, but rather a data catalogue. This means a Resource strategy can be used to connect to, search through, and resolve references to data in any given data catalogue. Then piping this result into a Parser strategy will ensure the data reference is retrieved (downloaded) and parsed.

Changelog

v0.7.0.dev0 (2024-02-29)

Full Changelog

Merged pull requests:

* This Changelog was automatically generated by github_changelog_generator