Closed greenkeeper[bot] closed 6 years ago
Update to this version instead 🚀
firebase init firestore
uses storage rules for Firestore, if the project already has storage rules but not Firestore rules.The new version differs by 5 commits.
6f1bef7
[firebase-release] Updated CLI to 4.0.1
39cc880
Changelog for v4.0.1 (#845)
0b23a2e
Fix #837 - firebase init
uses storage rules for firestore rules sometimes (#841)
1510929
Fix #838 - reference error during deployment when there are too many functions (#840)
ddebbab
[firebase-release] Removed change log and reset repo after 4.0.0 release
See the full diff
Update to this version instead 🚀
Update to this version instead 🚀
firebase init
with a non-existent feature.firebase init
erroring if initializing Firestore/Storage on a brand-new project.The new version differs by 8 commits.
83ca55d
[firebase-release] Updated CLI to 4.0.3
6510c53
Changelog for v4.0.3 (#855)
c946d20
Update lodash dependency (#856)
e1abefe
Display a sane error message when firebase init is called with an invalid feature. (#854)
a47baab
Update README.md (#852)
54b1d71
Document functions:delete in README(#851)
f7eb481
Fix firebase init when Rules never used on a project (#850)
066b530
[firebase-release] Removed change log and reset repo after 4.0.2 release
See the full diff
Version 4.0.0 of firebase-tools was just published.
The version 4.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of firebase-tools.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
v4.0.0firebase deploy
will now ask for confirmation before Cloud Functions deletion. Running the command with--non-interactive
will fail if there are functions detected for deletion."engines": {"node": "8"}
tofunctions/package.json
. You will needfirebase-functions
SDK v2.0.0 or up.firebase functions:delete
command for explicit deletion of functions.firebase init
over-wrote existing Firestore rules and indexes that were either specified through a local file or specfied in the Firebase Console.Commits
The new version differs by 13 commits.
69776f2
[firebase-release] Updated CLI to 4.0.0
3582612
Changelog for v4.0.0 (#294)
c4c17d3
Update firebase init template for functions (#293)
85deaf9
Display Node version that functions are deployed to (#291)
1f41e01
Support Node.js 8 functions runtime. (#290)
5fd8ae0
Ask for confirmation before deleting functions during 'firebase deploy' (#287)
46511c5
Add "firebase functions:delete" command (#286)
f9d3460
Support configuration of function region, memory, and timeout (#285)
b35592d
Default JS linting to false during
firebase init
for functions (#836)6ce81c0
Fix bug where "firebase init" overwrites existing Firestore indexes (#832)
7ec8b0b
Fix bug where "firebase init" overwrote existing Firestore rules (#831)
1c1b372
Update profiler to new query format (#826)
0ff6a55
[firebase-release] Removed change log and reset repo after 3.19.3 release
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: