Release - Patch Version - 2.0.3

[Ludee]

Description of the release

The installation of the package fails.

Details of the release

Name: Patchy McPatchface
Git tag: v2.0.3 "OEMetadata Patch Release v2.0.3"
Release Manager: @Ludee
Date: 2025-02-06

Workflow checklist

• I am aware of the workflow in RELEASE_PROCEDURE.md
• 4. 🐙 Create a Draft GitHub Release
• 5. 💠 Create a release branch
• 6. 📝 Update the version files (CHANGELOG.md, CITATION.cff)
• 7. 🐙 Create a Release Pull Request
• 8. 💠 Set the Git Tag
• 9. 🐙 Publish GitHub Release
• 10. 💻 Update the documentation
• 11. 🐙 Set up new development

[jh-RLI]

Some things are missing here for the patch release which i already merged. I think having another patch release is feasible ... we already found some new issues in the json-ld context.

[jh-RLI]

Ach, i forgot that there was the issue regarding the new setup config. The pypi deployment still fails.

[Ludee]

The specification for the new pyproject.toml needs to have the same name as the package folder.

Source: https://packaging.python.org/en/latest/specifications/pyproject-toml/

The folder "metadata" needs to be renamed to "oemetadata"

[jh-RLI]

This will break virtually any third party implementation of oemeta data as all imports will fail.

[Ludee]

At the moment, they are failing anyway.
The folder rename will have to be changed in a lot of places:

• base_folders
• scripts
• tests
• documentation and README

[jh-RLI]

And any link we provide in OEP, academy, compendium and more?

[Ludee]

"Move slow and break things"
That is good title for the next release 🤣