Skip to content

Commit c7a537a

Browse files
committed
📝 doc(CHANGELOG): log 0.5.0
Signed-off-by: Haili Zhang <[email protected]>
1 parent 6b38463 commit c7a537a

File tree

1 file changed

+11
-0
lines changed

1 file changed

+11
-0
lines changed

CHANGELOG.md

+11
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,17 @@
44

55
[1]: https://www.npmjs.com/package/@openfunction/functions-framework?activeTab=versions
66

7+
## 0.5.0 / 2022-05-27
8+
9+
We are having a standalone `openfunction` signature type starting from this release!
10+
11+
Now you can use `function (ctx, data)` as the function signature along with `openfunction` signature type, this allows you to use sync functions in a far more flexible way - whenever there are functions output requirements, sync functions can also send output to Dapr output binding or pubsub components.
12+
13+
Check the demo of HTTP request triggering async function:
14+
15+
- Quickstart: <https://openfunction-talks.netlify.app/2022/203-node-mixed/>
16+
- Sample: <https://github.com/OpenFunction/samples/tree/main/functions/knative/with-output-binding-node>
17+
718
## 0.4.1 / 2022-04-17
819

920
This feature release offically introduces the support of OpenFunction async function runtime, now your Node.js functions can enjoy the power of Dapr runtime starting from bindings and pubsub. Functions Framework will call [Dapr Node.js SDK](https://github.com/dapr/js-sdk) to bridge the communication with various Dapr input/output bindings or pubsub brokers components.

0 commit comments

Comments
 (0)