fix(deps): stick firebase-functions to v1
#68
Merged
Conversation
This file contains 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
... in response to this email:
Since Cloud Functions for Firebase is built on Google Cloud Functions, we’re writing to let you know about some changes that are being made to the Google Cloud Functions.
What you need to know
Starting September 1, 2024, future versions of the gcloud functions deploy CLI command will create Cloud Functions using 2nd generation by default. If you do not wish to create a 2nd generation function, you can override this behavior by using the --no-gen2 CLI flag.
Additionally, the firebase-functions Node.js SDK will begin defaulting to the v2 API instead of the v1 API. The v2 API is available now at firebase-functions/v2.
Cloud Functions for Firebase has two product versions:
Cloud Functions (1st generation), the original version, used whenever targeting the firebase-functions/v1 SDK.
Cloud Functions (2nd generation), a new version built on Cloud Run and Eventarc providing an enhanced feature set, which has been generally available since 2022.
This is used whenever you need to target the firebase-functions/v2 SDK.
You can learn more about the benefits of Cloud Functions for Firebase (2nd generation) in the Cloud Functions version comparison documentation.
What you need to do
If you are unable to upgrade at this time, change your import from firebase-functions to firebase-functions/v1 to preserve your existing codebase.
If you automate the creation of new Cloud Functions for Firebase evaluate the differences between generations when creating 2nd generation functions to avoid any issues.
If you conclude that you need to create functions in 1st generation, update your imports from firebase-functions to firebase-functions/v1 before September 1, 2024.
We’re here to help
We know this change may take some planning, and we're committed to supporting you during this transition. If you have any questions or require assistance, please contact Google Cloud support.
Your projects with created or updated functions (last 90 days) are below:
telegram-scribe-bot (telegram-scribe-bot)
Thanks for choosing Cloud Functions for Firebase.
—The Firebase Team