chore: bump version to 0.12.0

[laipz8200]

✨ What’s New in v0.12.0? ✨

Important

Heads up! Starting with this version, we'll no longer support Python 3.10. Make sure to upgrade to Python 3.11 or 3.12 to stay current with our updates.

Hey everyone! We’ve been busy fine-tuning the platform and packing in some new features in version 0.12.0. Let’s see what’s new and improved:

🚀 Enhanced File Support for Workflow/Chatflow LLM Node and Chat/Agent

We’re excited to introduce the new file support capabilities for LLM Node and Basic Chat/Agent! This update significantly enhances multi-modal capabilities and smart document processing, providing more flexibility and power for your application development. Here are the key highlights:

File Variable Support in LLM Node

LLM Node now supports directly referencing File and Array File variables in Prompts, unlocking greater possibilities for developers.
For example, you can upload multiple file variables (such as PDFs and images) and have the model collaboratively handle complex tasks, like summarizing report content or extracting key data. Multi-file support makes workflow design more efficient and seamless!

Tip

1. File Support Scope: The file types supported by the model may be more limited than the types allowed for upload. Be sure to read your model provider's official documentation to ensure that uploaded files can be processed correctly.
2. Document Handling in Unsupported Models: If the model does not natively support processing document files, you will still need to use the Document Extractor for extracting content.
3. Filtering Unsupported Files: To handle unsupported file types, consider using List Filter or IF-ELSE to screen them, ensuring smooth workflows.
4. Relation to Vision Features: File support operates independently of the Vision toggle. As long as the model supports Vision capabilities, you can use files as input.

New Document-Type Support for Basic Chat and Agent

Basic Chat and Agent now include a Document toggle. If the model supports processing document-type files, you can enable this feature.
For instance, you can upload a PDF report and let the Agent automatically analyze market data or assess content value, making such workflows simpler and smarter.

Enhanced Multi-Modal Capabilities

The new version extends support for multi-modal tasks. For example, you can upload audio files and have the model perform emotional analysis. This combination of text, audio, and file processing capabilities allows you to build more diverse and rich application scenarios.

⚙️ Improvements

• OpenAI o1 Streaming Support: We now support streaming output for OpenAI o1-preview and o1-mini, thanks to @laipz8200 in Support streaming output for OpenAI o1-preview and o1-mini #10890.

• Performance Optimization: The WeightRerankRunner logic has been optimized to achieve constant time complexity, thanks to @yihong0618 in fix: better WeightRerankRunner run logic use O(1) and delete unused code #10849.

• UI Enhancements: We’ve made the Table of Contents panel in the API document page collapsible, giving you greater control over your workspace, thanks to @hjlarry in feat: make toc panel can collapse #10875.

• JSON Schema for Gemini Models: Added support for JSON schema integration, ensuring smoother alignment with Gemini models, thanks to @hjlarry in feat: support json schema for gemini models #10835.

• Redis Clusters: Our ext_redis.py now includes support for Redis clusters, expanding flexibility for data management, implemented by @liuhaoran1212 in ext_redis.py support redis clusters --- Fixes #9538 #9789.

• Enhanced Custom Notes: You can now further enhance custom notes for increased expressiveness, courtesy of @hjlarry in feat: enhance the custom note #8885.

That’s the scoop for v0.12.0! Until next time, keep exploring and innovating! 🌟

[yihong0618]

ci failed may be caused by #11038
will try to figure out why too.

[yihong0618]

@laipz8200 seems this need to be change too?

docker-compose.yaml
172:  CHROMA_AUTH_PROVIDER: ${CHROMA_AUTH_PROVIDER:-chromadb.auth.token_authn.TokenAuthClientProvider}
607:  chroma:
608:    image: ghcr.io/chroma-core/chroma:0.5.1 -> image: ghcr.io/chroma-core/chroma:0.5.20

[bowenliang123]

#11038 never runs or passes the vdb tests. It's a mistake. also cc @crazywoola
I would suggest to raise a separate PR to ensuring chroma vdb tests run against the corresponding chroma image. @yihong0618

[yihong0618]

#11038 never runs or passes the vdb tests. It's a mistake. also cc @crazywoola I would suggest to raise a separate PR to ensuring chroma vdb tests run against the corresponding chroma image. @yihong0618

#11038 never runs or passes the vdb tests. It's a mistake. also cc @crazywoola I would suggest to raise a separate PR to ensuring chroma vdb tests run against the corresponding chroma image. @yihong0618

will do it now, thanks

[laipz8200]

#11038 never runs or passes the vdb tests. It's a mistake. also cc @crazywoola I would suggest to raise a separate PR to ensuring chroma vdb tests run against the corresponding chroma image. @yihong0618

These tests should run when pyproject.toml or the code related to vdb is changed. I missed including pyproject.toml in #10354.

[yihong0618]

#11038 never runs or passes the vdb tests. It's a mistake. also cc @crazywoola I would suggest to raise a separate PR to ensuring chroma vdb tests run against the corresponding chroma image. @yihong0618

These tests should run when pyproject.toml or the code related to vdb is changed. I missed including pyproject.toml in #10354.

fixed in #11057 @bowenliang123 can you also help to review?

[bowenliang123]

#11038 never runs or passes the vdb tests. It's a mistake. also cc @crazywoola I would suggest to raise a separate PR to ensuring chroma vdb tests run against the corresponding chroma image. @yihong0618

These tests should run when pyproject.toml or the code related to vdb is changed. I missed including pyproject.toml in #10354.

Never mind. And please make sure the poetry lockfile is included for running vdb test as well. The minor and even patch version is important, especially for Chroma.

[yihong0618]

#11038 never runs or passes the vdb tests. It's a mistake. also cc @crazywoola I would suggest to raise a separate PR to ensuring chroma vdb tests run against the corresponding chroma image. @yihong0618

These tests should run when pyproject.toml or the code related to vdb is changed. I missed including pyproject.toml in #10354.

Never mind. And please make sure the poetry lockfile is included for running vdb test as well. The minor and even patch version is important, especially for Chroma.

added already

[bowenliang123]

Well noticed. Thanks.