Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency @azure/functions to v4 #905

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 26, 2023

This PR contains the following updates:

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

Release Notes

Azure/azure-functions-nodejs-library (@​azure/functions)

v4.6.0

Compare Source

Fixed

Full Changelog: Azure/azure-functions-nodejs-library@v4.5.1...v4.6.0

v4.5.1

Compare Source

Fixed
  • Fixed undefined HTTP params when streaming is enabled #​285

v4.5.0

Compare Source

Added
  • Support for log hooks #​228. This feature requires Azure Functions Host v4.34+
  • Allow specifying worker capabilities during setup #​255
Fixed
  • Retry options were ignored #​250

v4.4.0

Compare Source

Added
Changed
  • The values of some system-generated request headers have changed when using the preview http streams feature. These values should now match the behavior when not using http streams.

v4.3.0

Compare Source

Added
  • Preview support for HTTP Streams. Learn more in our blog post 🎉
Fixed

v4.2.0

Compare Source

Added
  • clone() method to HttpRequest and HttpResponse #​207

v4.1.0

Compare Source

Added
  • Pre-invocation, post-invocation, app-start, and app-terminate hooks using app.hook. #​7
  • Warmup trigger #​176
  • connection property to EventGridOutputOptions #​177
Fixed
  • Bug where output isn't set if used in both extraOutput and return #​179

v4.0.1

Compare Source

Add link to blog post and discussion to README

v4.0.0

Compare Source

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 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 and #​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
  • Simplify context object #​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
      • 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 based on the undici 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
  • Remove setup() method. v4 of the programming model is automatically setup when you register any function from the app object

Configuration

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

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

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


  • If you want to rebase/retry this PR, check this box

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

@renovate renovate bot force-pushed the renovate/azure-functions-4.x branch 5 times, most recently from 068930f to b5374cd Compare October 3, 2023 00:39
@renovate renovate bot force-pushed the renovate/azure-functions-4.x branch 8 times, most recently from 38b5b06 to b150717 Compare October 9, 2023 21:09
@renovate renovate bot force-pushed the renovate/azure-functions-4.x branch 6 times, most recently from a020eea to d96aaa4 Compare October 19, 2023 20:14
@renovate renovate bot force-pushed the renovate/azure-functions-4.x branch 5 times, most recently from b0f5d4c to feea970 Compare October 25, 2023 21:05
@renovate renovate bot force-pushed the renovate/azure-functions-4.x branch 4 times, most recently from 395ef76 to 923f7a2 Compare November 6, 2023 21:12
@renovate renovate bot force-pushed the renovate/azure-functions-4.x branch 2 times, most recently from 31d2291 to d1c363a Compare November 7, 2023 18:52
@renovate renovate bot force-pushed the renovate/azure-functions-4.x branch 4 times, most recently from dfd493e to abeed85 Compare June 5, 2024 12:11
@renovate renovate bot force-pushed the renovate/azure-functions-4.x branch 5 times, most recently from ed4d157 to b701597 Compare June 18, 2024 10:56
@renovate renovate bot force-pushed the renovate/azure-functions-4.x branch 5 times, most recently from 5062c04 to d3d8a50 Compare June 26, 2024 06:52
@renovate renovate bot force-pushed the renovate/azure-functions-4.x branch 3 times, most recently from 8e9f74c to 25c2443 Compare July 6, 2024 05:24
@renovate renovate bot force-pushed the renovate/azure-functions-4.x branch 2 times, most recently from 380ca92 to 297ba6c Compare July 13, 2024 18:11
@renovate renovate bot force-pushed the renovate/azure-functions-4.x branch 3 times, most recently from ac2b31a to 51e5bb9 Compare July 23, 2024 22:56
@renovate renovate bot force-pushed the renovate/azure-functions-4.x branch from 51e5bb9 to b17c7ae Compare July 28, 2024 12:07
@renovate renovate bot force-pushed the renovate/azure-functions-4.x branch 2 times, most recently from facefd2 to ef9906b Compare August 5, 2024 12:55
@renovate renovate bot force-pushed the renovate/azure-functions-4.x branch 3 times, most recently from 150fdf2 to 227eb97 Compare September 21, 2024 16:00
@renovate renovate bot force-pushed the renovate/azure-functions-4.x branch from 227eb97 to 0d5f2af Compare September 21, 2024 20:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants