Skip to content

Commit 879c5c2

Browse files
[firebase-release] Removed change log and reset repo after 4.0.0 release
1 parent 8ea3943 commit 879c5c2

File tree

1 file changed

+0
-32
lines changed

1 file changed

+0
-32
lines changed

CHANGELOG.md

Lines changed: 0 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -1,32 +0,0 @@
1-
### Breaking Changes
2-
3-
- Deprecated `allowInvalidAppCheckToken` option. Instead use
4-
`enforceAppCheck`.
5-
6-
> App Check enforcement on callable functions is disabled by default in v4.
7-
> Requests containing invalid App Check tokens won't be denied unless you
8-
> explicitly enable App Check enforcement using the new `enforceAppCheck` option.
9-
> Furthermore, when enforcement is enabled, callable functions will deny
10-
> all requests without App Check tokens.
11-
12-
- Dropped support for Node.js versions 8, 10, and 12.
13-
- Dropped support for Admin SDK versions 8 and 9.
14-
- Removed the `functions.handler` namespace.
15-
- `DataSnapshot` passed to the Firebase Realtime Database trigger now
16-
matches the `DataSnapshot` returned by the Admin SDK, with null values
17-
removed.
18-
- Removed `__trigger` object on function handlers.
19-
- Reorganized source code location. This affects only apps that directly import files instead of using the recommend entry points specified in the
20-
- Reworked the `apps` library and removed `lodash` as a runtime dependency.
21-
22-
### Enhancements
23-
24-
- Logs created with the `functions.logger` package in v2 functions
25-
are now annotated with each request's trace ID, making it easy to correlate
26-
log entries with the incoming request. Trace IDs are especially useful for
27-
cases where 2nd gen's concurrency feature permits a function
28-
to handle multiple requests at any given time. See
29-
[Correlate log entries](https://cloud.google.com/logging/docs/view/correlate-logs) to learn more.
30-
- `functions.logger.error` now always outputs an error object and is included in Google Cloud Error Reporting.
31-
- The logging severity of Auth/App Check token validation has changed from `info` to `debug` level.
32-
- Event parameters for 2nd generation functions are now strongly typed, permitting stronger TypeScript types for matched parameters.

0 commit comments

Comments
 (0)