Skip to content

[Snyk] Security upgrade @openfunction/functions-framework from 0.3.6 to 0.5.0 - #615

Open
benjaminhuo wants to merge 1 commit into
masterfrom
snyk-fix-def6a49cbfaff988654e4674cebbd653
Open

benjaminhuo wants to merge 1 commit into
masterfrom
snyk-fix-def6a49cbfaff988654e4674cebbd653

Conversation

@benjaminhuo

Copy link
Copy Markdown
Member

snyk-top-banner

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

Snyk changed the following file(s):

  • docs/esm/package.json
  • docs/esm/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Infinite loop
SNYK-JS-URIJS-19963963
  721  

Breaking Change Risk

Merge Risk: High

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

…nerabilities

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-URIJS-19963963
@benjaminhuo

Copy link
Copy Markdown
Member Author

Merge Risk: High

This upgrade crosses a significant breaking change boundary introduced in the v0.4.0 release series.

Breaking Change:
The primary breaking change is the update of the OpenFunction Context, which is provided to functions at runtime. The framework version you are upgrading to is aligned with a newer, incompatible version of the core OpenFunction API.

  • OpenFunction v0.3.x (your 'from' version) uses Context Spec v0.1.0.
  • OpenFunction v0.4.x and v0.5.x (your 'to' version) use Context Spec v0.2.0.

This change was driven by the upgrade of the core OpenFunction API from v1alpha1 to v1alpha2 in the v0.4.0 release.

Impact:
Any code in your functions that interacts with the Context object for inputs, outputs, or other runtime information is likely to break and will require modification to align with the new v0.2.0 specification.

Recommendation:
Before merging, developers must review the OpenFunction Context v0.2.0 specification and update their function code to be compatible with the new context structure. This is a high-risk upgrade that requires code-level changes.

Source: OpenFunction Functions Framework Documentation

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

@CLAassistant

Copy link
Copy Markdown

CLA assistant check
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.

@mergeable

mergeable Bot commented Sep 20, 2026

Copy link
Copy Markdown

Thanks for creating a pull request! A maintainer will review your changes shortly. Please don't be discouraged if it takes a while.

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.

3 participants