sql:migrate. (#9018)firebase init dataconnect:sdk generate consistent fixed package names (#9021)configDir configuration option to specify a custom directory for .env files in Functions (#9000)get_sample_crash_for_issue and get_issue_details (#8995)firebase init dataconnect (#8988)firebase deploy --only dataconnect didn't include GQL files in nested folders (#8981)firebase deploy create Cloud SQL instances asynchronously (#9004)firestore:databases:create --edition enterprise. (#8952)get_sdk_config tool now properly returns decoded file content for Android and iOS.deploy prompt as the first available.__name__ fields with DESCENDING order were incorrectly filtered from index listings, causing duplicate index issues (#7629) and deployment conflicts (#8859). The fix now preserves __name__ fields with explicit DESCENDING order while filtering out implicit ASCENDING __name__ fields.firebase init dataconnect didn't enable the Data Connect API by default (#8927).apptesting commands.__name__ fields with DESCENDING order were incorrectly filtered from index listings, causing duplicate index issues (#7629) and deployment conflicts (#8859). The fix now preserves __name__ fields with explicit DESCENDING order while filtering out implicit ASCENDING __name__ fields.firebase init apptesting_UNKNOWN case with a string associated value. The fix changes that case name from UNKNOWN to _UNKNOWN. If you have existing generated enums, you may need to rebuild your project.value property to the EnumValue base interface.firestore:indexes wrongly removed the __name__ field. (#7629)string_pattern filters in Data Connect. These allow you to filter string fields using regex or LIKE semantics.firebase-tools could not be used within v1 Cloud Functions due to trying to write to a read only file.ext:configure where params without default values could not be set. (#8810)string_pattern filters in Data Connect. These allow you to filter string fields using regex or LIKE semantics.generate_dataconnect_schema, dataconnect_generate_operation, firebase_consult_assistant MCP tools. (#8647)firebase init dataconnect is now integrated with Gemini in Firebase API to generate Schema based on description. (#8596)serviceusage.googleapis.com quota.functions:list.firebase init feature selection. (#5232)demo- projects. (#8720)--export-on-exit fails if the target directory does not exist. (#4688)package.json when multiple package managers are used in a web project.@table(key).projects:create didn't correctly parse the projectId and displayName input. (#8634)firebase use --add didn't correctly set the active project. (#8694)firestore:delete. (#6753)firebase init now uses FIREBASE_PROJECT env var as the default project name.firestore.database was treated as a required field in firebase.json. This is addressed in 14.5.1.init where users were forced to specify emulator UI port (#8626)webframeworks enabled, firebase init hosting re-prompts users for source. (#8587)auth.uid in CEL expressions when unauthenticated.firebase init firestore + firebase deploy flow on a fresh new project without going to Console (#8653)firebase experimental:mcp command, which runs an MCP server for AI assistants to interact with Firebase resources.firebase init hosting:github didn't correctly parse the repo input. (#8536)@transaction continued to execute after errors and produces more confusing errors.@transaction returned bogus data that had been invalidated by the rollback. They now correctly return null with a corresponding error "(rolled back)".@check on side-effect fields if the mutation doesn't have @transaction.null in CEL expressions.response binding to Server Values and @check(expr:) CEL expressions.firebase init firestore would raise an error due to rules/indexes file path being undefined. (#8518)firebase use required serviceusage.viewer permissions. (#8519)init dataconnect.demo- projects.add and remove list update transforms and fixes an issue where updating a column to null was ignored. (#8484)