Release 0.1.1

[TobiasSchmidtDE]

Release 0.1.1

• Added MIT License & updated README accordingly
• Added support & CI/CD tests for python >3.8 up to 3.14
• Removed unused dependencies
• Removed unused code depending on torch (removed torch as dependency)
• Added AUTHOR.md
• Added NOTICE file & updated cebra notebook example to give CEBRA demo attribution
• Cleaned up build process (remove tests from tar.gz and .whl)

Release Checklist

Full release process documentation: CONTRIBUTING.md

• Make sure the build workflow passes on the release branch. Also make sure that the milestone related to this release is fully done. Move issues that won't make it into the release to the next milestone, then close the milestone.
• Head to ituna.__init__ and make sure that the __version__ is set correctly.
• Create a PR to main.
• Tag the PR with the release label.
• The publish workflow will run — if it doesn't start, try removing and re-adding the release label (step 4).
• The release-labeled PR will build and push to TestPyPI. Verify the staging version looks correct:

  pip install --index-url https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple/ ituna==<version>

  Note: If you update the PR, the TestPyPI version will not be automatically updated. Remove and re-add the release label to trigger a new upload.
• If all looks good, tests pass and the PR is reviewed, merge the PR using rebase merging.
• Delete the branch.
• Checkout the updated main branch, create the tag and push it:

  git checkout main && git pull
  git tag v<version>
  git push origin v<version>

  Use the correct format: v1.2.3 for stable releases, v1.2.3a4 or v1.2.3b4 for alpha/beta.
• Pushing the tag triggers the publish workflow which builds and uploads the package to PyPI.
• Verify the release on PyPI:

  pip install ituna==<version>
  python -c "import ituna; print(ituna.__version__)"