Skip to content

Changelogs

0.0.21

  1. New Provider: openai-compatible – This provider is designed to integrate APIs of models compatible with the OpenAI chat schema (tested with: deepseek, Doudao/Volcano platform, Qwen/Alibaba). Detail.
  2. New Provider: smart-router – This provider analyzes the semantics of user input and selects an appropriate model to query. Detail.
  3. New Model Configuration Mechanism: You can now configure a custom model to adapt to all models provided by a specific model provider. Detail.
  4. Bugfix: Corrected the cache loading logic, which previously caused a program crash upon the first run of BRConnector.
  5. Headers Value Pass-through in sagemaker-lmi Provider: Now, values in the headers are URL-encoded and included in the CustomAttributes tag of the SageMaker SDK.
  6. BRClient Update to Version 1.2.5: Key updates include:
    - In AKSK mode, users can now customize the Bedrock endpoint.
    - Fixed a bug where pressing Enter in Chinese input methods would send the message immediately.

0.0.20

  1. Fixed the representation of boolean types in environment variables. Now only “false” and “0” are considered as false.
  2. Added support for nova-canvas in the painter plugin (text-to-image only).
  3. Collapsed the display of operation buttons in the API key list.
  4. Modified the data type of the index in the output result choices to integer.
  5. Added a new Provider: nova-canvas, which allows image manipulation through natural language (including the following tools: text-to-image, image-to-image, foreground replacement/inpaint, background replacement/outpaint, background removal, variations, and color guidance). https://aws-samples.github.io/sample-connector-for-bedrock/zh/providers/nova-canvas/

0.0.19

  1. Fixed a critical bug: log file handles were filling up the system, causing it to become unresponsive after a period of time.
  2. Rewrote the logging system, aiming to unify the format as much as possible.

0.0.18

  1. Added model and API key queries to the backend management web interface.
  2. Added configuration for the Amazon Nova models in NoDB mode. As the Nova models are relatively new and only available in certain regions, please note to use them in conjunction with the AWS_DEFAULT_REGION environment variable.
  3. The nova model has been added to the initialization script in the database, but it will only take effect in the newly created databases of BRConnector.
  4. Fixed a backend error that attempted to save database data even in NoDB mode.
  5. Changed the output type of ‘id’ from number to string during streaming output, now it can be correctly deserialized by aider.
  6. Added support for the embedding API, now it can adapt to the titan embeddings model. You need to configure a new model using the titan_embeddings Provider, and use the API (/v1/embeddings) to call it.

0.0.17

  1. When the client actively stops output, the application now actively closes the server-side response.
  2. Cost control now works correctly.

0.0.16

  1. Added a new configuration option for bedrock-converse: maxTokens

0.0.15

  1. Added haiku 3.5 model in NoDB mode.

  2. Removed some unnecessary log outputs.

0.0.14

  1. Added caching mechanism, with the following details:

  • If the system does not configure environment variables PGSQL_HOST or PGSQL_DATABASE, BRConnector will switch to pass-through mode. In this mode, only the ADMIN_API_KEY environment variable can be used to access models, and only built-in static models can be accessed (default LLM models supported by Bedrock Converse; if new models are released in the future, BRConnector code needs to be updated).

  • If a database is configured and the PERFORMANCE_MODE environment variable is set, custom models and API Keys configured in the database will take effect. These two parts of data will be loaded directly into memory (up to 2000 entries, refreshed every 1 minute, significantly reducing database access). In this case, BRConnector will only verify if the API Key is valid, without checking if the API Key has permission to access a specific model. It will no longer save conversation records or track and control costs.

  1. Fixed a Dify access bug. Issue #43

  2. For Feishu webhook, added multi-turn dialogue, image recognition, and document recognition features.

  3. Added optional configurations for NoDB, PERFORMANCE_MODE in CloudFormation.

  4. Upgraded the aws-lambda-adapter image for Lambda to version 0.8.4. The new adapter version resolves conflicts with the Authorization Header in IAM_Auth for Lambda function URLs.

  5. Optimized CloudFormation Output, now showing clear endpoints.

0.0.13

  1. New Feature: Introduced a webhook mechanism for easy integration with third-party applications.

  2. New Webhook: Feishu, allowing BRConnector integration into Feishu through configuration.

  3. New Plugin: continue-coder, enabling BRConnector configuration in Continue for code generation.

  4. New Models Support: The painter plugin now supports the latest bedrock SD models: stability.stable-image-core-v1:0, stability.sd3-large-v1:0, and stability.stable-image-ultra-v1:0.

  5. Deployment Script Upgrade: Added a permission configuration, now correctly calling cross-region model profiles.

  6. Improvement: Added an API key query API, allowing precise matching by name, group_id, and role.

  7. Improvement: Default model support: Now a model named ‘default’ can respond to any model name. If not defined, an error message will be output.

  8. Refactored parts of the code and added a standard API: /v1/completions, to support continue-coder. Currently, only bedrock-coverse and continue-coder have implemented this API.

  9. Upgraded the underlying AWS SDK dependency to 3.645.0 and fixed various other bugs.

0.0.12

  1. New provider: urls-reader, which can parse URLs in user conversations and download the text content from the URLs to add to the conversation context.
  2. Optimized the painter provider, now supporting the Titan image model. The large language model has been changed to BRConnector’s local model.
  3. It is now possible to delete models, groups, and API Keys in the manager interface.
  4. Bug fix: Automatic update script for CloudFormation EC2.