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

chore(deps-dev): bump @azure/functions from 3.5.1 to 4.1.0 #148

Closed

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Nov 20, 2023

Bumps @azure/functions from 3.5.1 to 4.1.0.

Release notes

Sourced from @​azure/functions's releases.

v4.1.0

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

Add link to blog post and discussion to README

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 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

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Bumps [@azure/functions](https://github.com/Azure/azure-functions-nodejs-library) from 3.5.1 to 4.1.0.
- [Release notes](https://github.com/Azure/azure-functions-nodejs-library/releases)
- [Commits](Azure/azure-functions-nodejs-library@v3.5.1...v4.1.0)

---
updated-dependencies:
- dependency-name: "@azure/functions"
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Nov 20, 2023
@dhensby
Copy link
Collaborator

dhensby commented Nov 21, 2023

@dependabot ignore @azure/functions minor version

Copy link
Contributor Author

dependabot bot commented on behalf of github Nov 21, 2023

Sorry, the command you entered is not valid for this pull request. Please check the syntax and try again.

Valid commands:
For single dependency PRs, use commands like:
@dependabot ignore this major version
@dependabot ignore this minor version
@dependabot ignore this dependency

@dhensby
Copy link
Collaborator

dhensby commented Nov 21, 2023

@dependabot ignore this major version

@dependabot dependabot bot closed this Nov 21, 2023
Copy link
Contributor Author

dependabot bot commented on behalf of github Nov 21, 2023

OK, I won't notify you about version 4.x.x again, unless you re-open this PR.

@dependabot dependabot bot deleted the dependabot/npm_and_yarn/azure/functions-4.1.0 branch November 21, 2023 09:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant