The dependency upgrades may break the Travis build script. I have temporarily commented out the portion that updates coveralls since this has changed #544.
We are using the builtin GitHub workflow to run CI for node projects with the new upgrades. This can run tests, linters, and build the project to ensure it is without errors. It is not setup to deploy the project to our firebase site thought. The Travis script was not doing this properly anymore anyway so now may be the time to figure out a new way to do it or just fix the Travis script.
It may be possible to leave the GitHub workflow as our default CI for all pushes and pull requests. Then only use the Travis script to deploy to firebase when we merge a branch into master.
We could also just manually deploy new versions to the firebase. Perhaps only on certain types of version changes or bug fixes. Either way this needs to be decided and setup.
The dependency upgrades may break the Travis build script. I have temporarily commented out the portion that updates coveralls since this has changed #544.
We are using the builtin GitHub workflow to run CI for node projects with the new upgrades. This can run tests, linters, and build the project to ensure it is without errors. It is not setup to deploy the project to our firebase site thought. The Travis script was not doing this properly anymore anyway so now may be the time to figure out a new way to do it or just fix the Travis script.
It may be possible to leave the GitHub workflow as our default CI for all pushes and pull requests. Then only use the Travis script to deploy to firebase when we merge a branch into master.
We could also just manually deploy new versions to the firebase. Perhaps only on certain types of version changes or bug fixes. Either way this needs to be decided and setup.