Skip to content

Update deployment manager deprecation date#9941

Merged
jhuleatt merged 5 commits intomainfrom
jhuleatt-functions-config-deprecation
Feb 26, 2026
Merged

Update deployment manager deprecation date#9941
jhuleatt merged 5 commits intomainfrom
jhuleatt-functions-config-deprecation

Conversation

@jhuleatt
Copy link
Copy Markdown
Contributor

Description

Per the recent MSA we sent out, after March 31, 2027, developers will not be able to deploy updates to Cloud Functions for Firebase that rely on the legacy Cloud Runtime Configuration API. The warning in the CLI used to say March 2026.

Scenarios Tested

n/a

Sample Commands

n/a

@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @jhuleatt, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the deprecation timeline for the legacy Cloud Runtime Configuration API within the Firebase CLI. The change reflects an extension of the deprecation date from March 2026 to March 2027, providing developers with additional time to migrate away from the functions.config() API and associated CLI commands. This ensures that the CLI's warning messages align with the latest policy changes.

Highlights

  • Deprecation Date Update: The deprecation date for the functions.config() API and the Cloud Runtime Config service has been extended from March 2026 to March 2027.
  • CLI Command Deprecation: The removal date for the legacy functions:config:* CLI commands has also been moved to before March 2027.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • src/functionsConfig.ts
    • Updated the FUNCTIONS_CONFIG_DEPRECATION_MESSAGE constant to reflect the new deprecation date of March 2027.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request correctly updates the deprecation date for the deployment manager from March 2026 to March 2027. I've included a suggestion to improve maintainability by extracting the repeated date string into a constant. However, this PR is missing a required update to CHANGELOG.md. The repository's style guide requires that any user-facing change, such as this one, must have a corresponding entry in the changelog.

@jhuleatt jhuleatt requested a review from brittanycho February 18, 2026 18:42
@jhuleatt jhuleatt marked this pull request as ready for review February 18, 2026 18:42
Copy link
Copy Markdown
Contributor

@brittanycho brittanycho left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@jhuleatt jhuleatt enabled auto-merge (squash) February 18, 2026 19:14
Copy link
Copy Markdown

@shettyvarun268 shettyvarun268 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@jhuleatt jhuleatt merged commit f3feec7 into main Feb 26, 2026
47 checks passed
@jhuleatt jhuleatt deleted the jhuleatt-functions-config-deprecation branch February 26, 2026 18:21
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.

5 participants