v0.4.1: Allow Typer 0.10.0 and above

✨ New features and improvements

• Updates to the CI (#89).
• Extend the Typer pin to allow v0.10.0 and above (#87).

👥 Contributors

@aymenkrifa, @honnibal, @ines, @svlandeg

v0.4.0: Allow a git repo file as asset and drop support for Python 3.6

✨ New features and improvements

• Update cloudpathlib upper pin to 1.0.0 (#78).
• Update smart_open upper pin to 8.0.0 (#84).
• Drop support for EOL Python 3.6 (#85).

🔴 Bug fixes

• Fix issue #66: Support fetching a file from a git repo as an asset.

👥 Contributors

@BLKSerene, @danieldk, @honnibal, @ines, @jeffrey12cali, @ringohoffman, @svlandeg

v0.3.4: Bug fixes for document CLI and help messages

🔴 Bug fixes

• Update CLI command messages for Weasel usage (#71).
• Customize help messages to refer to either weasel or spacy project depending on calling command (#72).
• Fix KeyError in document command when updating older READMEs (#74).

👥 Contributors

@adrianeboyd, @honnibal, @ines, @ljvmiranda921, @svlandeg

v0.3.3: Updates for full Python 3.12 support

✨ New features and improvements

• Update for cloudpathlib 0.16 to fully support Python 3.12 including remote storage (#68).

👥 Contributors

@adrianeboyd, @honnibal, @ines, @svlandeg

v0.3.2: Update Typer requirement

🔴 Bug fixes

• Extend to typer<0.10.0 to align with spaCy (#64).

👥 Contributors

@adrianeboyd, @honnibal, @ines, @svlandeg

v0.3.1: Updates for Python 3.12

✨ New features and improvements

This release introduces support for Python 3.12, with the exception of remote storage support, which currently still requires Python 3.11 or earlier. As soon as cloudpathlib supports Python 3.12, remote storage support will also be available in Weasel.

• Remove catalogue requirement (#57).
• Update docs for cloudpathlib and Python 3.12 (#60).
• Update warning and tests for Python 3.12 (#61).

🔴 Bug fixes

• Fix warning message code for make_tempdir permission error (#59).

👥 Contributors

@adrianeboyd, @honnibal, @ines, @rmitsch, @svlandeg

v0.3.0: Remove requirements checks

✨ New features and improvements

• Remove requirements check due to pkg_resources deprecation (#49).
• Update package metadata (#54).

🔴 Bug fixes

• Skip tests requiring git if it is not available (#55).

⚠️ Backwards incompatibilities

• Weasel no longer attempts to check requirements from requirements.txt and support for the check_requirements configuration key has been dropped.

👥 Contributors

@adrianeboyd, @honnibal, @ines, @rmitsch, @svlandeg

v0.2.0: Support Pydantic v2, switch to cloudpathlib

✨ New features and improvements

• Switch from Pathy to cloudpathlib (#43).
• Update setup for Python 3.6+ support (#45).
• Replace pydantic.BaseSettings with simpler checks (#46).
• Extend to confection v0.1 (#50).
• Allow Pydantic v2 using transitional v1 support (#52).

🔴 Bug fixes

• Accept both SPACY PROJECT and WEASEL in markers (#42).
• Fix error code E501 (#47).

👥 Contributors

@adrianeboyd, @honnibal, @ines, @rmitsch, @svlandeg

v0.1.1: Fix CLI usage, `pre-commit` run

🔴 Bug fixes

• Fixing an incorrectly defined entry point preventing weasel from being used via CLI (#38)
• Add a pin for pydantic to ensure a working pre-commit run (#39)

👥 Contributors

@adrianeboyd, @honnibal, @ines, @rmitsch, @svlandeg

v0.1.0

This is the very first release of our new Weasel library, a standalone replacement for spaCy Projects.

Weasel lets you manage and share end-to-end workflows for different use cases and domains, and orchestrate training, packaging and serving your custom pipelines. You can start off by cloning a pre-defined project template, adjust it to fit your needs, load in your data, train a pipeline, export it as a Python package, upload your outputs to a remote storage and share your results with your team. Weasel can be used via the weasel command and we provide example templates in our projects repo.

✨ New features and improvements

Just like spacy project, the weasel command-line interface offers:

• End-to-end, reproducible workflow management
• Push and pull from local and distant remotes
• Clone existing workflows to get started rapidly
• Auto-document your workflows for easier sharing

⚠️ Backwards incompatibilities

There are a few backward incompatibilities with spacy project that you should be aware of:

• The SPACY_CONFIG_OVERRIDES environment variable is no longer checked. You can set configuration overrides with WEASEL_CONFIG_OVERRIDES.
• Support for the spacy_version configuration key has been dropped.
• Support for SPACY_PROJECT_USE_GIT_VERSION environment variable has been dropped.
• Error codes are now Weasel-specific, and do not follow spacy project codes.

Weasel will check for the first three incompatibilities, and will issue a warning if you're using it with spaCy-specific configuration options.

📖 Documentation and examples

Visit the Weasel documentation for more information!