@databutton/firebase-types 1.178.1 → 1.179.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/lib/types/published/requests.d.ts +1 -0
  2. package/package.json +2 -2
package/lib/types/published/requests.d.ts CHANGED
@@ -640,6 +640,7 @@ export type GenerateUsageReportResponse = {
640
640
  export type InviteMemberToAccountRequest = {
641
641
  accountId: string;
642
642
  email: string;
643
+ role?: AccountRole;
643
644
  };
644
645
  export type InviteMemberToAccountResponse = {
645
646
  statusCode: number;
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@databutton/firebase-types",
3
- "version": "1.178.1",
3
+ "version": "1.179.0",
4
4
  "main": "lib/types/published/index.js",
5
5
  "type": "module",
6
6
  "engines": {
@@ -29,7 +29,7 @@
29
29
  "@protobufjs/utf8": "1.1.2",
30
30
  "@tootallnate/once": "2.0.1",
31
31
  "node-forge": "1.4.0",
32
- "fast-xml-parser": "5.11.0",
32
+ "fast-xml-parser": "5.11.1",
33
33
  "//3": "@opentelemetry/core moderate advisory GHSA-8988-4f7v-96qf (unbounded memory allocation in W3C Baggage propagation, fixed >=2.8.0). firebase-tools>@google-cloud/pubsub pins @opentelemetry/core to the ^1.30.1 line, which never received a backport; no top-level bump resolves this. Pubsub only uses the stable W3CTraceContextPropagator class, unchanged across the 1.x/2.x split, so forcing 2.x here is safe.",
34
34
  "@opentelemetry/core": "2.10.0",
35
35
  "//4": "uuid moderate advisory (missing buffer bounds check, fixed >=11.1.1). firebase-tools' bundled gaxios/google-auth-library still require uuid ^9.0.1 and firebase-tools has no newer release available (latest is 15.28.2, same range). They only call the argumentless uuid.v4(), unaffected either way and stable across majors, so pinning to our own already-used 11.1.1 is safe.",