Bump firebase-functions from 6.6 to 7.2.5#767
Merged
Conversation
v7 removed functions.config() entirely. All call sites were migrated to process.env in PR #766 and deployed across all 11 envs; this PR is the trivial dep bump that completes the v7 prep work. Breaking changes in v7 relevant to this codebase: - functions.config() removed — handled in PR #766. - Node 18 minimum — we run Node 22. - Emulator now returns 500 on unhandled async errors in onRequest handlers (production unchanged). Our onRequest handlers (auth/*, api/*) use try/catch wrappers, so the surface risk is in Cypress E2E only. All other v7 breakages are TS-only or affect APIs we don't use (Gen 2 scheduled attemptDeadlineSeconds, v1 Event type rename). Gen 2 RTDB triggers and defineString/params APIs unchanged. firebase-admin ^13.9.0 satisfies v7's peer-dep range (^11 || ^12 || ^13). No other deps need updating. Tests: 36 suites / 314 tests passing under v7.2.5.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Trivial dep bump that completes the v7 prep work. v7's main breaking change (removal of
functions.config()) was handled in PR #766 and rolled out to all 11 envs on 2026-05-15.functions/package.json:firebase-functions: ^6.6.0→^7.0.0firebase-functions@7.2.5(latest stable).v7 breaking-change enumeration (per regression-risk feedback)
Affects us, already handled or N/A:
functions.config()removedprocess.env, deployed to all 11 envs.functions/package.jsonengines + CI).^11 || ^12 || ^13^13.9.0. ✓Affects us, behaviour change (low risk):
onRequesthandlers (production behaviour unchanged)onRequesthandlers (auth/*,/api/*) all wrap their async work intry/catch. The only surface risk is Cypress E2E against the emulator, which the test plan probes.Does not affect us:
functions/is plain JS, notsconfig.EventTS type renamed toLegacyEvent— TS-only.attemptDeadlineSecondsremoved from Gen 2 scheduled — we use Gen 1pubsub.schedule(...).onValueCreated/Updated/Deleted/Written),defineString,firebase-functions/params— APIs unchanged across v7.x.Tests
npm run test:functions— 36 suites / 314 tests passing under v7.2.5.Test plan
lszm_test→firebase functions:log --project lszm-testclean, no cold-start crashesOut of scope
WEBHOOK_REGIONGH vars across all 11 envs — dead config from the early Gen 2 webhook migration. Harmless. Clean separately.auth.testcredentials.*(onlspv-test) andserviceaccount.*(onmfgt-flights,project-...332047) infirebase functions:config— zero references in code. Clean viafirebase functions:config:unsetseparately.functions/package.jsonshellscript still referencesfirebase functions:config:get(a CLI subcommand). The CLI may still support reading from a now-permanently-empty config; not exercised by deploys. Out of scope.