The extension published every lifecycle event twice — once as firebase.extensions.firestore-counter.v1.<name> (a historical naming mistake kept for backwards compatibility) and once as firebase.extensions.firestore-bigquery-export.v1.<name>. The kit publishes only the latter, so any Eventarc trigger filtering on the firestore-counter types stops firing on migration.
getEventTypes in the kit already returns an array and every publisher already maps over it, so restoring the legacy type is one entry plus the README note that currently documents the drop as intentional.
Parity ledger: #2974, firestore-bigquery-export.
The extension published every lifecycle event twice — once as
firebase.extensions.firestore-counter.v1.<name>(a historical naming mistake kept for backwards compatibility) and once asfirebase.extensions.firestore-bigquery-export.v1.<name>. The kit publishes only the latter, so any Eventarc trigger filtering on thefirestore-countertypes stops firing on migration.getEventTypesin the kit already returns an array and every publisher already maps over it, so restoring the legacy type is one entry plus the README note that currently documents the drop as intentional.Parity ledger: #2974, firestore-bigquery-export.