You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a major upgrade across five major versions (v8 to v13) of the firebase-admin SDK. It includes significant and mandatory breaking changes, primarily related to Node.js runtime support and a fundamental shift in how the API is used.
Key Breaking Changes:
Node.js Version Requirements: The minimum required Node.js version has been increased multiple times. Upgrading to 13.10.0 will require a Node.js runtime of v18 or higher.
v10.0.0 dropped support for Node.js 10.
v11.0.0 dropped support for Node.js 12.
v12.0.0 dropped support for Node.js 14.
v13.0.0 dropped support for Node.js 16.
Modular API (Introduced in v10.0.0): This is the most significant code-level breaking change. The SDK moved from a namespaced, chained API to a modular, function-based one. This requires substantial code refactoring.
Deprecated Methods: Methods on the App object (e.g., app.auth()) were deprecated in v10 in favor of the modular getService(app) pattern.
Recommendation:
This upgrade cannot be performed without significant developer intervention.
Environment Upgrade: Ensure your production and development environments are running Node.js 18 or a higher supported version.
Code Refactoring: Allocate time to refactor your entire codebase to adopt the new modular import style introduced in v10. Follow the official migration guide for detailed instructions.
Staged Upgrade: Consider upgrading major versions incrementally (8 -> 10, 10 -> 11, etc.) in a separate branch to isolate and address breaking changes at each step.
Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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/firebase_post_3.4.0/package.jsonVulnerabilities that will be fixed with an upgrade:
SNYK-JS-NODEFORGE-19635204
Breaking Change Risk
Important
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.