[Snyk] Security upgrade @google-cloud/functions-framework from 1.5.1 to 5.0.0

[benjaminhuo]

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• builders/testdata/nodejs/functions/with_prepare/package.json
• builders/testdata/nodejs/functions/with_prepare/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Uncaught Exception SNYK-JS-QS-19432019	738

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Uncaught Exception

[benjaminhuo]

This is a major upgrade across multiple breaking versions (v1 to v5) and corresponds to the architectural shift from Google Cloud Functions (1st gen) to the newer Cloud Run-based Cloud Functions (2nd gen).

Key Breaking Changes:

• Node.js Runtime: Support for older, end-of-life Node.js versions has been dropped. You must be on a modern, supported Node.js LTS version.
• Event-Driven Function Signatures: The structure of event payloads has changed. The framework now uses the industry-standard CloudEvents format for all event-driven functions. Code that processes event data and context objects will need to be updated to handle the new format.
• Underlying Infrastructure: The framework is now built on top of Cloud Run and Eventarc. While this provides benefits like longer timeouts and larger instances, it can introduce subtle behavioral changes in request handling and execution environment.
• Configuration: The way functions are registered and configured may have changed. For example, specifying the function signature type (http, cloudevent) is now a standard part of the framework's configuration.

Recommendation:
This upgrade requires a significant migration effort. Do not merge this change without a thorough review and testing of each function. You will need to:

1. Update your Node.js runtime to a supported version.
2. Refactor event-driven functions to work with the CloudEvents payload structure.
3. Review HTTP function logic for any dependencies on the older execution environment.
4. Consult the official Google Cloud documentation for migrating from 1st to 2nd gen functions.

Source: Google Cloud Blog

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}