search

probot / example-azure-function

Probot & Azure Functions example
ISC License
1 stars 11 forks source link

chore(deps): update dependency @azure/functions to v4 #80

Open renovate[bot] opened 11 months ago

renovate[bot] commented 11 months ago

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@azure/functions ^3.2.0 -> ^4.0.0 age adoption passing confidence

Release Notes

Azure/azure-functions-nodejs-library (@​azure/functions) ### [`v4.5.1`](https://redirect.github.com/Azure/azure-functions-nodejs-library/releases/tag/v4.5.1) [Compare Source](https://redirect.github.com/Azure/azure-functions-nodejs-library/compare/v4.5.0...v4.5.1) ##### Fixed - Fixed undefined HTTP params when streaming is enabled [#​285](https://redirect.github.com/Azure/azure-functions-nodejs-library/issues/285) ### [`v4.5.0`](https://redirect.github.com/Azure/azure-functions-nodejs-library/releases/tag/v4.5.0) [Compare Source](https://redirect.github.com/Azure/azure-functions-nodejs-library/compare/v4.4.0...v4.5.0) ##### Added - Support for log hooks [#​228](https://redirect.github.com/Azure/azure-functions-nodejs-library/issues/228). This feature requires Azure Functions Host v4.34+ - Allow specifying worker capabilities during setup [#​255](https://redirect.github.com/Azure/azure-functions-nodejs-library/pull/255) ##### Fixed - Retry options were ignored [#​250](https://redirect.github.com/Azure/azure-functions-nodejs-library/pull/250) ### [`v4.4.0`](https://redirect.github.com/Azure/azure-functions-nodejs-library/releases/tag/v4.4.0) [Compare Source](https://redirect.github.com/Azure/azure-functions-nodejs-library/compare/v4.3.0...v4.4.0) ##### Added - Support for params when using preview [http streams](https://aka.ms/AzFuncNodeHttpStreams) feature [#​229](https://redirect.github.com/Azure/azure-functions-nodejs-library/issues/229) - Support for SQL trigger [#​88](https://redirect.github.com/Azure/azure-functions-nodejs-library/issues/88) ##### Changed - The values of some system-generated request headers have changed when using the preview [http streams](https://aka.ms/AzFuncNodeHttpStreams) feature. These values should now match the behavior when *not* using http streams. ### [`v4.3.0`](https://redirect.github.com/Azure/azure-functions-nodejs-library/releases/tag/v4.3.0) [Compare Source](https://redirect.github.com/Azure/azure-functions-nodejs-library/compare/v4.2.0...v4.3.0) ##### Added - Preview support for HTTP Streams. Learn more in our [blog post](https://aka.ms/AzFuncNodeHttpStreams) 🎉 ##### Fixed - Fixed error with out-of-sync binding names [https://github.com/Azure/azure-functions-nodejs-library/issues/210](https://redirect.github.com/Azure/azure-functions-nodejs-library/issues/210) ### [`v4.2.0`](https://redirect.github.com/Azure/azure-functions-nodejs-library/releases/tag/v4.2.0) [Compare Source](https://redirect.github.com/Azure/azure-functions-nodejs-library/compare/v4.1.0...v4.2.0) ##### Added - `clone()` method to `HttpRequest` and `HttpResponse` [#​207](https://redirect.github.com/Azure/azure-functions-nodejs-library/issues/207) ### [`v4.1.0`](https://redirect.github.com/Azure/azure-functions-nodejs-library/releases/tag/v4.1.0) [Compare Source](https://redirect.github.com/Azure/azure-functions-nodejs-library/compare/v4.0.1...v4.1.0) ##### Added - Pre-invocation, post-invocation, app-start, and app-terminate hooks using `app.hook.` [#​7](https://redirect.github.com/Azure/azure-functions-nodejs-library/issues/7) - Warmup trigger [#​176](https://redirect.github.com/Azure/azure-functions-nodejs-library/issues/176) - `connection` property to EventGridOutputOptions [#​177](https://redirect.github.com/Azure/azure-functions-nodejs-library/issues/177) ##### Fixed - Bug where output isn't set if used in both `extraOutput` and `return` [#​179](https://redirect.github.com/Azure/azure-functions-nodejs-library/issues/179) ### [`v4.0.1`](https://redirect.github.com/Azure/azure-functions-nodejs-library/releases/tag/v4.0.1) [Compare Source](https://redirect.github.com/Azure/azure-functions-nodejs-library/compare/v4.0.0...v4.0.1) Add link to blog post and discussion to README ### [`v4.0.0`](https://redirect.github.com/Azure/azure-functions-nodejs-library/releases/tag/v4.0.0) [Compare Source](https://redirect.github.com/Azure/azure-functions-nodejs-library/compare/v3.5.1...v4.0.0) *The new Node.js programming model is now Generally Available! 🎉 This changelog is meant as a detailed list of changes in the new version. See the [official upgrade guide](https://learn.microsoft.com/azure/azure-functions/functions-node-upgrade-v4) for a less detailed, more user-friendly list of the changes.* ##### Added - Support registering functions directly in your code instead of in `function.json` files [#​569](https://redirect.github.com/Azure/azure-functions-nodejs-worker/issues/569) and [#​480](https://redirect.github.com/Azure/azure-functions-nodejs-worker/issues/480) - Allow classes like `InvocationContext` and `HttpRequest` to be constructed in test environments outside the Azure Functions runtime ##### Changed - Update minimum version of Node.js to 18.x - Update minimum version of TypeScript to 4.x - Switch the order of arguments. For example, `(context, request)` is now `(request, context)` [#​34](https://redirect.github.com/Azure/azure-functions-nodejs-library/issues/34) - Simplify `context` object [#​204](https://redirect.github.com/Azure/azure-functions-nodejs-worker/issues/204) - Rename `Context` to `InvocationContext` - Remove `context.done()`. We assume your function (async or sync) is done as soon as it returns - Remove `context.executionContext`. You can find `functionName` and `retryContext` on the root `context` object instead - Remove `context.bindingDefinitions` in favor of `context.options` - Remove `context.log` sub-methods (`context.log.error`/`context.log.warn`/etc.) in favor of methods on the root `context` object (`context.error`/`context.warn`/etc.). Also Remove the `verbose` option in favor of `trace` and `debug` to match Node.js's `console` methods - Remove `context.req`, `context,res`, and `context.bindings`. The primary input is always an argument to your function, the primary output is always the return value of your function, and everything else can be accessed on `context.extraInputs` or `context.extraOutputs` - Clean up `context.bindingMetadata` - Rename to `context.triggerMetadata` - Remove legacy `sys` property - Remove logic that was recursively attempting to convert objects from rpc values, causing [#​607](https://redirect.github.com/Azure/azure-functions-nodejs-worker/issues/607) - Make camel-case logic consistent so that it applies to the whole object - specifically including arrays which were previously excluded - Remove http classes that were unique to Azure Functions in favor of new classes representing a subset of the [fetch standard](https://developer.mozilla.org/docs/Web/API/fetch) based on the [undici](https://undici.nodejs.org/) npm package. - Rename `Request` to `HttpRequest` - Change `query` from type `HttpRequestQuery` to Node.js core type `URLSearchParams` - Remove `HttpResponseSimple`/`HttpResponseFull`/`HttpResponse` types in favor of `HttpResponse` class and `HttpResponseInit` interface - Remove `statusCode` in favor of `status` - Remove `end`, `send`, `sendStatus`, and `json`. These were callback methods based on `context.done()` which is no longer supported - Remove header-related methods (`setHeader`, `header`, `set`, `getHeader`, `get`, `removeHeader`, `type`) from base response object. You must use `response.headers` for any header-related methods - Change `headers` from type `HttpRequestHeaders`/`HttpResponseHeaders` to fetch standard type `Headers` - Remove body properties `body`, `rawBody`, `bufferBody`, and `parseFormBody()` in favor of fetch standard methods `arrayBuffer()`, `blob()`, `formData()`, `json()`, and `text()` - Handle all falsy values appropriately. Treat it as data to be passed along instead of occasionally converting it to `null` [#​388](https://redirect.github.com/Azure/azure-functions-nodejs-worker/issues/388) - Remove `setup()` method. v4 of the programming model is automatically setup when you register any function from the `app` object ### [`v3.5.1`](https://redirect.github.com/Azure/azure-functions-nodejs-library/releases/tag/v3.5.1) [Compare Source](https://redirect.github.com/Azure/azure-functions-nodejs-library/compare/v3.5.0...v3.5.1) Update readme for v4 [announcement](https://aka.ms/AzFuncNodeV4)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

This PR was generated by Mend Renovate. View the repository job log.