Skip to content

Releases: w9jds/firebase-action

JDK support and Docker Image

09 Nov 06:34
0a5173f
Compare
Choose a tag to compare
  • Action no longer rebuilds the image every time it runs (pulls image from docker)
  • firebase-tools has been set to v8.15.1
  • On commit a new version is pushed to Docker Hub ( Thanks: @Hacksore )
  • Action now include JDK for function emulators!

Fix firebase-tools requiring git to install

22 Jun 07:32
Compare
Choose a tag to compare
  • changed from the slim image to the alpine image
  • moved to LTS node version
  • install git before installing firebase-tools

Add firebase-tools permissions workaround

21 Jun 18:06
Compare
Choose a tag to compare
  • Bump up the base image version to latest node-slim
  • Add NPM user variable to root to address current permission issues in firebase-tools

Update README for artifact action changes

21 May 17:08
92e616d
Compare
Choose a tag to compare

Add support for new GCP Key on Firebase Tools

07 Feb 21:48
40e688f
Compare
Choose a tag to compare

Firebase tools now allows you to specify a GCP Service Key instead of a Token to deploy your changes. We now support passing in this key in replacement of Firebase Token.

Create option for different directory

10 Nov 04:37
Compare
Choose a tag to compare
  • Added in the ability to have Firebase.json in a different directory than root

Upgrade for latest Github Action systems

21 Sep 00:47
Compare
Choose a tag to compare
  • A lot has changed since the initial beta of actions, this update will bring it up to par with the current way actions are configured.
  • The example also shows how to pass a build artifact to the deployment job.

Entrypoint Syntax Fix

16 Jan 12:55
7d6b2b0
Compare
Choose a tag to compare
  • Thanks to @uphy for the catch

GitHub Action for Firebase Initial Release

14 Jan 21:38
ab8b52a
Compare
Choose a tag to compare
Update README

Further explanation on when you should use PROJECT_ID