Releases: connery-io/connery-sdk
v0.3.0
0.3.0 (2024-06-04)
Features
BREAKING CHANGES
- Deprecate
configurationParameters
in plugin and use
inputParameters
from action instead - Deprecate
maintainers
- Rename
title
toname
in plugins, actions, inputs and outputs - Deprecate
/api/specs/openai/gpts endpoint
on the pluign server - Deprecate
/api/specs/openai/assistants-api
endpoint on the plugin
server
These endpoints are moved from the individual plugin to the Connery app,
which makes more sense and brings more control.
v0.3.0-beta.2
v0.3.0-beta.1
0.3.0-beta.1 (2024-06-03)
BREAKING CHANGES
- Deprecate
configurationParameters
in plugin and use
inputParameters
from action instead - Deprecate
maintainers
- Rename
title
toname
in plugins, actions, inputs and outputs - Deprecate
/api/specs/openai/gpts endpoint
on the pluign server - Deprecate
/api/specs/openai/assistants-api
endpoint on the plugin
server
These endpoints are moved from the individual plugin to the Connery app,
which makes more sense and brings more control.
v0.2.1-beta.1
v0.2.0
0.2.0 (2024-04-17)
Features
BREAKING CHANGES
- The
startPluginServer()
function is renamed tosetupPluginServer()
because, in theAWS_LAMBDA
hosting mode, this function does not start
the plugin server but just initializes the server and prepares the
handler function for Lambda.
v0.1.4
v0.1.3
v0.1.2
v0.1.1
v0.1.0
0.1.0 (2024-04-05)
Features
- Pivot the project from the Connery Runner to the Connery SDK (#105)
BREAKING CHANGES
The Connery Runner is deprecated. Instead, we switch to the Connery SDK, an NPM package that offers a JavaScript API for defining plugins and actions and packaging them into a plugin server with a standardized REST API generated from the metadata.
The plugin server is basically a Connery Runner built into every plugin. The Connery SDK makes the plugin a standalone web app with its standardized REST API that can be hosted anywhere. The standardized API enables various clients to interact with actions in a unified way, regardless of the underlying implementation.
This approach significantly improves plugin portability, reduces setup and maintenance effort, and enables us to enhance plugin functionality more quickly in future releases.
Even though the release has been published, not all the clients support the Connery SDK approach yet. But we are working on it and will migrate the clients to the new approach very soon.
Stay tuned for more updates on the Connery SDK!