-
Notifications
You must be signed in to change notification settings - Fork 219
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: firebase/firebase-functions
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: fae1bf0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: firebase/firebase-functions
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: f08be25
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 12 commits
- 26 files changed
- 6 contributors
Commits on Aug 11, 2021
-
Configuration menu - View commit details
-
Copy full SHA for e9f5e43 - Browse repository at this point
Copy the full SHA e9f5e43View commit details -
Set Access Control for HTTP Functions (v2) (#935)
* adding invoker to v2 http functions * fix format * change invoker to always turn into an array, add error handling * fix trigger annotated in v2 and change v1 to only put invoker array in trigger annotated * changing invoker type for better type completion
Configuration menu - View commit details
-
Copy full SHA for 94414f4 - Browse repository at this point
Copy the full SHA 94414f4View commit details -
Use npm ci on publish scripts. (#940)
I kept seeing error on the npm version command claiming that the directory was dirty. I believe this is because version of the npm used in our builder image is >7 which uses lockfileversion 2 instead of 1 checked into the repo. Using npm ci instead, but we should also think about updating the package-lock.json to lockfileversion 2.
Configuration menu - View commit details
-
Copy full SHA for 31d52b7 - Browse repository at this point
Copy the full SHA 31d52b7View commit details -
Configuration menu - View commit details
-
Copy full SHA for 1b7a73b - Browse repository at this point
Copy the full SHA 1b7a73bView commit details -
Configuration menu - View commit details
-
Copy full SHA for e2ccc53 - Browse repository at this point
Copy the full SHA e2ccc53View commit details -
* HTTP functions always return a promise even when apply CORS. Previously HTTPS functions had to be patched in the emulator to ensure that the promise is always handled. This change should circumvent that need and make v2 patching unnecessary. * Export undocumented dependency of the emulator * Make @types/cors a proper dep * Add dummy files to silence imports eslinter Co-authored-by: Michael Bleigh <bleigh@google.com>
Configuration menu - View commit details
-
Copy full SHA for 2e214ed - Browse repository at this point
Copy the full SHA 2e214edView commit details -
Configuration menu - View commit details
-
Copy full SHA for 670dc92 - Browse repository at this point
Copy the full SHA 670dc92View commit details -
Configuration menu - View commit details
-
Copy full SHA for 360d426 - Browse repository at this point
Copy the full SHA 360d426View commit details -
Configuration menu - View commit details
-
Copy full SHA for e6eb1ea - Browse repository at this point
Copy the full SHA e6eb1eaView commit details
Commits on Aug 12, 2021
-
Configuration menu - View commit details
-
Copy full SHA for dfd1708 - Browse repository at this point
Copy the full SHA dfd1708View commit details -
Configuration menu - View commit details
-
Copy full SHA for 92597f0 - Browse repository at this point
Copy the full SHA 92597f0View commit details -
Configuration menu - View commit details
-
Copy full SHA for f08be25 - Browse repository at this point
Copy the full SHA f08be25View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff fae1bf0...f08be25