- Preloading also Realtime Database; 11.0.1b
- Moved to Node.js 18;
firebase-tools
11.0.1
- Update to
firebase-tools
11.0.0
- Update to
firebase-tools
10.6.0
- Update to
firebase-tools
10.4.0
- Bumped to
firebase-tools
10.2.2 - Disabled
database
emulator (not personally needing it)
- Bumped to Firebase CLI 10.0.1; Node 16 now comes with npm 8 causing a name change of the image.
- Added license for Google's Dev Library
- Upgraded to 9.17.0
- Pumped up to 9.16.5 ⛽️
- Suppressing npm update notifications
- Updated
firebase-tools
to 9.16.0
-
ADD (undercover): A user
user
created, for manual use.Cloud Build still requires that the image is left without a
USER
.
- CHANGE: Using "headless" JRE, trims ~10MB off the image
- CHANGE: No longer needing GNU Make
- Updated to
firebase-tools
9.12.1.
-
CHANGE: Enabled UI emulation; disabled Pub/Sub; mentioning Storage
The idea is that people can enable/disable just the emulators they need to prefetch.
- CHANGE:
FIREBASE_EMULATORS_PATH
so downstream doesn't need to move the emulator images (ONBUILD
wasn't picked up by Cloud Build). - OPTIMIZATION: PubSub cached
.zip
removed (496MB image size)
- Upgraded to Firebase tools 9.11.0 and Node.js 16.
- Changed to recommending non-regional Container Registry (
gcr.io
) in all cases.
-
FIX: Preloaded emulator packages were not used. Tried solving this, but cannot since Cloud Build rudely overrides the home directory, and removes anything we would have placed there.
The solution needs one step from consuming parties (now mentioned in the
README
).
- Leaving
root
as the user; eliminates Cloud Build problems. 🙂 - Updated to Firebase CLI v. 9.6.1
- Added
curl
- Updated to
npm
7.x (7.7.5)
- Documenting: Notion about pushing the
latest
image.
Found this in excavations, and took it to use!
- Adjusting for use with Cloud Build (not GitHub Packages)
- Updating to later
firebase-tools
: 8.8.1 -> 9.6.0 - Use of
Makefile
- Pushing to Cloud Registry (for Cloud Build)
- Initial release; pushed
8.8.1-node14
to GitHub Packages 🙂