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`](https://github.com/explosion/weasel/blob/v0.1.0/docs/cli.md) command and we provide example templates in our [`projects`](https://github.com/explosion/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](https://github.com/explosion/weasel/tree/v0.1.0) for more information!